thanks Holger. I actually found that my problem was trying it from the
console instead of straight from a script. It works ok in the script. I
appreciate the information.
Paul Tretter
----- Original Message -----
From: "Holger Kruse" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 01, 2001 10:57 AM
Subject: [REBOL] Re: Server Ports
> On Thu, Feb 01, 2001 at 10:28:51AM -0600, Paul Tretter wrote:
> >
> > When creating server ports such as:
> >
> > server: open/lines/direct tcp://:113
> > client: first server
> >
> > How do you keep the script from blocking other port activities with in
the same script. In otherword this just hangs at client:first server and
blocks other port activity until 'server receives data. The no-wait option
seems to do the same thing. Any ideas?
>
> You can insert
>
> p: wait [server otherports...]
>
> To wait for one of several ports to have data. The value returned by 'wait
tells
> you which of the ports has data.
>
> no-wait only has an effect on 'copy. Without no-wait 'copy only returns on
> end-of-file. With no-wait 'copy returns immediately with whatever data is
> available.
>
> --
> Holger Kruse
> [EMAIL PROTECTED]
>
> --
> To unsubscribe from this list, please send an email to
> [EMAIL PROTECTED] with "unsubscribe" in the
> subject, without the quotes.
>
--
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the
subject, without the quotes.
