[EMAIL PROTECTED] wrote:
> Hello Petr,
>
> Just taking a break, and saw your message...
ah, thanks very much, it's so long we've talked, I am still here, and no
plan to leave. :-)
>
> 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).
Eventually? Give REBOL as much possibilities as possible :-) Btw: what's the
case with asynchronous messaging and multitasking in REBOL?
btw: you will have to introduce some "other kind" of ports to Rebol, as with
/Media we will need some event handling (mouse movement, etc.), or am I
wrong? As speaking about /Media, will it support non flickering smooth
scrolling? You know - Windows doesn't support double - buffering :-)
> I can imagine supporting other
> network models as well, such as Netware.
>
My knowledges reaches the end here, sorry :-) I thought the issue with
Netware is IPX/SPX protocol, not just ports?
Anyway, thanks for the reply .... and ... you can make a break once a month
at least, we are glad to see you here :-)
Best Wishes,
-pekr-
>
> -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-
> >
