World: r3wp

So it's like the old BSD with the advertising clause, the one that 
people complained about. Nifty.

Yeah, but if that's the biggest complaint we have... ;-)

That's not insignificant, as the advertising clause of the old BSD 
made it legally incompatible with a lot of other licenses. Particularly 
(L)GPL, but we as a community need to be avoiding (L)GPL code anyways 
for a lot of reasons. We'll have to be careful.

If it's done as an extension it shouldn't be an issue for RT, correct?

If it's rolled into a host, then you need to care. Having it built 
in would be very cool so, yeah, you're right that we need to care.

One: yes, it would still be a problem even as an external extension. 
Two: we would have to do it as a host-embedded extension if we want 
to use this for the core intertask messaging solution, and that is 
the same as linking the code in.

Remember that advertising clauses are transitive, so all of our apps 
that we build with R3 would need to advertise Spread too. Even apps 
that we build for third-parties.

Yes, if it's built in, we're in sync. But if it's an external extension, 
doesn't it become a problem for us as individuals rather than RT?

Nope, because it becomes a problem for any person who uses that extension 
in their product.

It doesn't matter anyways, because we are discussing the standard 
intertask messaging mechanism for R3. That can't be external, it 
would have to run when external extensions are prohibited by security 
restrictions.

This is why BSD got rid of the advertising clause in the first place.

Yes, that's what I mean. We who distribute it, and passed along to 
those who use our work.

I'm willing to pay that price, but I can only speak for me. :-)

First, though, maybe some design thoughts about what our ideal IPC 
interface would look like.

To be fair, when last I tracked your job situation it didn't involve 
distributing REBOL software to customers directly, so that clause 
probably *would* work for you :)

Yes, design thoughts, back to the subject :)

Gregg - to be honest - 200KB? Total bloat. I work in enterprise sphere 
for 15 years, and never heard of something like "spread". In fact 
- noone in enterprise sphere cares. Guys, really - let's have clean 
 and mean REBOL solution, the REBOL way. Then we can interop with 
other systems, as the need arises. Let's not adhere to pseudo standards, 
because they have some juicy website ...

Re: Spread, it doesn't specifically say how you have to advertise, 
so one small clause on one page somewhere on the website would suffice

But asking each application built with R3 to also include a notice 
like this seems a big pain

I wonder if including this "This product uses software developed 
by Spread Concepts LLC for use in the Spread toolkit. For more information 
about Spread see http://www.spread.org"as a text string in the source 
counts?

Anyway, I guess most apps have some type of licensing that is viewable 
from the app, and you can just include the line in there.

I don't think it's a biggie .. more of an issue is how good is it, 
how complex, has anyone used it etc

Interestingly the first site I went to using this software does not 
display this text!  http://code.google.com/p/spread-excel/

Brian, I do commercial app development in REBOL as well as in-house.


Petr, I'm not here to defend Spread. I mentioned it because when 
I looked at it before, it was something I marked to remember because 
it wasn't too large or complex and didn't try to do too much (compared 
to, say, AMQP). 

I only played with it breifly, I didn't put it into production. 

I want a REBOL solution too. :-)

The questions are:

1) What do we need?

2) Can we build it?

Did you get it working at all?

I havne't tried using it from REBOL. Their test apps did work IIRC.

I have worked in enterprise sphere for 35 years and never heard of 
something like "REBOL" from anybody that I've every worked with.


Let's make sure that we don't change this and keep REBOL clean and 
mean and to itself.

Well, for 25 of those years REBOL didn't exist !

2010 - 1997 = 10 ?

rounded down

Mathematics aside, it should be obvious by now that REBOL is not 
in any way attractive in mainstream IT. I believe it's insularity 
doesn't help though that is only one reason. I made the comment tongue-in-cheek 
as I see no relevance to the worthiness or otherwise of a library 
just because somebody who has worked for 15 years in "enterprise 
sphere" never having heard of it.

Whether Spread would be right for REBOL is another matter though 
it would offer a limited  alternative for secure inter-process communications 
with non-REBOL processes without having to resort to either cgi or 
"roll-your-own".

The point is, any software should be judged on its intrinsic merits 
rather than how widly it is used?

Yes. For many, merits include robustness, reliability, documentation, 
support and availability of skilled people.

..and of course, its ability to integrate with what they already 
have.

Maybe we should make a list of candidate libraries and decide what 
is the best fit to our as yet unstated needs?

Perhaps it would be even better to state our needs for inter-process 
communication first?

Well I first raised the quesion of how an external extension might 
be able to communicate with the rebol application

PeterWoo - you talk nonsense, which belongs in advocacy group :-) 
If you work for 35 years in enterprise, then tell me, if you met 
spread there. The messaging is done by so called middlewares. IBM 
has MQ series, SAP has XI. Those engines use the so called connectors. 
Everybody went the web-services route, hence having ability to talk 
SOAP might be more important for REBOL. I never argued against having 
as much libraries as possible wrapped to REBOL, the only thing I 
argued against is eventual 200KB library inclusion in REBOL, just 
to do IPC between REBOL tasks ...

but hopefully not arrogant nonsense :-)

Well - I don't mind. It is not about if I ever heard about it. It 
is all about - how much interoperability with outer world do we get? 
E.g. - can you talk to most Windows or Linux (Unix) apps with it, 
like Amiga Arexx? Can you talk to SAP, Orcle APPs, WebSphere, SharePoint, 
etc. enterprise apps? In fact and once again - -I expect having extensions 
to as many systems as possible, but we surely also know, how picky 
is Carl about what is going to be included into standard distro, 
and 50KB is considered being a big addition :-)

Spread requires a daemon to be running ... so this doesn't fit

what I would like to see for IPC mechanism is some port/events mechanism. 
And then, on top of that, the way to go is the Uniserve like engine. 
Python has Medusa - simply put - multiprotocol engine, to communicate 
with external world ...

Graham IMO almost every IPC need somewhat daemon runing. The library 
"could" be linked in extension and try to open communication with 
daemon, when it doesnt find the daemon let start its own (first process 
trying to comunicate), what is nice in Spread it combines P2P and 
multicast and members/group policy, and of course single/multi machines.

Pekr I think in port event model the only what is neccessary is open 
events to OS events (what possibly is already done, but we don't 
know how to use it), not only GUI events. Than you can use local 
pipes (managed by OS including event signalling). Question is if 
multi machines IPC would go this way. Anyway all this is solved in 
QNX (signalling abstraction local/external). Question if they use 
sockets for this.

Pavel - yes, we have so called system port, but we don't know much 
about it :-) I hope we get Amiga/QNX kind of design in the end. At 
least that is what I would expect from the messaging expert, Carl 
:-)

Petr, Peter doesn't talk nonsense IMO. There are a lot of things 
REBOL could use for interop. SOAP would be a protocol, not an extension. 
REBOL IPC may be a protocol too. MQ et al would be for specific systems, 
not general IPC. I'm all for a Uniserve model.


Historically, memory mapped files were one of the most efficient 
IPC mechanisms on Windows, but if a more portable approach can be 
written based on named pipes, I can live with that. Sockets are great 
as long as you don't run into firewall issues (even locally), and 
might encourage us to think in terms of protocols and messages.


As Pavel said, and one of the main design points, is the need for 
a daemon. Obviously memory mapped files aren't going to work across 
the net.

Pavel, I pulled out my old QNX manual and it lists Messages, Ports, 
and Exeptions as their three IPC mechanisms. Messages can be sent 
on "virtual circuits" which have a node ID in addition to the task 
ID to send to; no implementation details given. Ports were like named 
pipes it seems, with 16 being numbered and reserved by the OS.

Gregg thx for info

Do you really need a daemon if you're just doing IPC on the one PC?