Hello Petr,
Just taking a break, and saw your message...
The idea of a port in REBOL is an abstraction. It works for any
type of serialized data, not just TCP/IP. The console is a byte
stream, so works well within the port model. Ports also work for
non-byte streams, such as a POP port. Eventually we'll be adding
a message port, so you can send and receive REBOL messages and they
will queue automatically (like Amiga message ports... ah, so now
you know why I called them ports). I can imagine supporting other
network models as well, such as Netware.
-Carl
At 10/21/99 02:52 PM +0200, you wrote:
>Hi,
>
>IIRC it was said Console uses ports too. At least, it has it's own
>scheme, so REBOL user works with it in similar aproach as with other
>shceme types. But it's not based on TCP/IP messaging (sockets) imho, as
>REBOL wouldn't probably work on systems where no TCP/IP stack is
>installed. So does REBOL use internally any other type of messaging,
>which will be used in /Command or /Media for e.g.? Or is everything
>going to be built upon TCP/IP or UDP only???
>
>Thanks,
>
>-pekr-
>
