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

port and capture was: help from Dixon or others about port

 [1/3] from: g::santilli::tiscalinet::it at: 7-Sep-2001 16:28


Hello Petr! On 07-Set-01, you wrote: PK> No, it doesn't imo - it waits (blocks) but will stop waiting PK> once it times out (you can set timeout for each protocol). If PK> you really want to wait, just use: Nope, timeout applies when receiving data, not connections. FIRST LISTEN waits forever on a listen port if it does not get a connection (it would make no sense to have a timeout there, it you think about it!). Regards, Gabriele. -- Gabriele Santilli <[giesse--writeme--com]> - Amigan - REBOL programmer Amiga Group Italia sez. L'Aquila -- http://www.amyresource.it/AGI/

 [2/3] from: rotenca:telvia:it at: 7-Sep-2001 11:40


> Wow, I didn't think anyone still looked at that... There was never much > enthusiasm about the text-editor with no line-wrap or mouse... ;-)
I searched capture strategies, your is fine. The back problem here are Firewalls.
> first, break it apart (there's a lot going on in that one line):
50 rows in C, at least :-)
> > and why does it make a wait before? > > wait l > > this ensures that the connection attempt has actually reached 'L , > everything would probably still work without it, but I'm not sure... I > haven't looked at this in a while now.
Now I've found the info in Core Manual (RTFM for me!). You can "first" a listen port only when a new connection has been set by remote user. I think that "first" makes an automatic "wait" if there are not connections (Not tested). Thank for your answers!
> - Cal Dixon
--- Ciao Romano

 [3/3] from: petr:krenzelok:trz:cz at: 7-Sep-2001 12:16


Romano Paolo Tenca wrote:
> Now I've found the info in Core Manual (RTFM for me!). You can "first" a > listen port only when a new connection has been set by remote user. I think > that "first" makes an automatic "wait" if there are not connections (Not > tested). >
No, it doesn't imo - it waits (blocks) but will stop waiting once it times out (you can set timeout for each protocol). If you really want to wait, just use: port: first wait listen-port -pekr-