Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

[REBOL] Re: CORE experimental 2.4.39

From: petr:krenzelok:trz:cz at: 23-Nov-2000 21:56

----- Original Message ----- From: Holger Kruse <[holger--rebol--com]> To: <[rebol-list--rebol--com]> Sent: Thursday, November 23, 2000 5:40 PM Subject: [REBOL] Re: CORE experimental 2.4.39
> > Will also other port types be made asynchronous? > > UDP already is (by its very nature): sending is asynchronous, within the > TCP/IP stack. Receiving can block (or not) depending on whether no-wait
was
> used. > > TCP is "officially" asynchronous for receiving only, using no-wait. > Internally it is also asynchronous for connecting, accepting and sending, > mostly controlled through get/set-modes, but the API is not quite > finished yet (in particular for sending). It needs a little more work to > be "nice" to use :). > > Higher protocol layers (HTTP, FTP) are currently based on the synchronous > "root protocol", i.e. they are synchronous by themselves. One of the > things we plan to do in the future is implement an "asynchronous root > protocol" which has all of the functionality of the current root protocol > (connect, read, write, proxy support, dialog parsing etc.), but is fully > asynchronous and handler-driven. An asynchronous version of HTTP could
then
> be implemented on top of that, which would, e.g., allow an arbitrary
number
> of parallel HTTP downloads in the background. Express already does
something
> like this, using its own asynchronous implementation.
Man, what are you waiting for? :-))) It would be cool to have. It's good it's planned at least. Sounds like interesting addition for REBOL 3.0, doesn't it? :-) Cheers, -pekr-