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

[REBOL] Re: LDC goes Rugby!

From: holger:rebol at: 23-May-2001 6:26

On Wed, May 23, 2001 at 12:38:04PM +0200, Petr Krenzelok wrote:
> the same as above. The difference I don't understand is - why you used > 'async-modes, if similar functionality can be achieve via /no-wait refinement > ...
/no-wait changes the behavior of 'copy. Without /no-wait 'copy waits until the other end closes the connection, with /no-wait 'copy waits until SOME data is available and returns it then. This mean /no-wait affects the way reading from a port interacts with end-of-file conditions. You need /no-wait together with /direct if you want to implement interactive protocols and use 'copy (instead of 'read-io). 'async-modes enables non-blocking operation of all port actions, including reading, writing, connecting and accepting connections on listen ports. It has nothing to do with end-of-file conditions. Again: don't use, don't use, don't use,... This was a quick internal hack for /Express and is NOT part of the official REBOL language. In Core 3.0 the 'async-modes word will go away, and we will provide an official API for async port operation that is much nicer and will, e.g., allow streaming, up/downloads in the background etc. -- Holger Kruse [holger--rebol--com]