Re: timeout for "socket"?
- From: ZB <zbREMOVE_THIS@xxxxxxxxxxxxxxxxxxxx>
- Date: 29 Jun 2008 23:14:00 GMT
Dnia 27.06.2008 Pat Thoyts <cnggublgf@xxxxxxxxxxxxxxxxxxxxx> napisał/a:
Have a look at the wiki for 'port scanning' - what you want to use is
a combination of [socket -async] and [after]
I'm not sure, what you mean.
If I use "-async", there will be a handle for a connection returned
immediately - therefore I'll have to test the connection different way,
for example using fileevent, like in your script.
But I've got a feeling, "async & after" gives me nothing more: just instead
of setting the timeout when testing the connection immediately (no "async"),
I'm testing the connection using "fileevent" (for example) - 2000 ms later,
but still not setting test duration. Just the testing process itself starts
2 seconds later.
I would to make it try to connect, say, 5 seconds - and not to test the
connection 5 seconds later. It's not the same.
--
ZB
.
- Follow-Ups:
- Re: timeout for "socket"?
- From: Donal K. Fellows
- Re: timeout for "socket"?
- References:
- timeout for "socket"?
- From: ZB
- Re: timeout for "socket"?
- From: Pat Thoyts
- timeout for "socket"?
- Prev by Date: Re: problem with special characters in file command?
- Next by Date: Re: timeout for "socket"?
- Previous by thread: Re: timeout for "socket"?
- Next by thread: Re: timeout for "socket"?
- Index(es):
Relevant Pages
|
