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

Server Ports

 [1/3] from: ptretter::norcom2000::com at: 1-Feb-2001 10:28


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? Paul Tretter

 [2/3] from: holger:rebol at: 1-Feb-2001 8:57


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 [holger--rebol--com]

 [3/3] from: ptretter:norcom2000 at: 1-Feb-2001 11:38


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" <[holger--rebol--com]> To: <[rebol-list--rebol--com]> 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: > >
<<quoted lines omitted: 4>>
> > > > 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?

Notes
  • Quoted lines have been omitted from some messages.
    View the message alone to see the lines that have been omitted