I'm trying to locate the source code and TTrafficLight component
referenced in an article written by Francois Piette and found
originally in thefollowing inactive linkage:
http://edn.embarcadero.com/print/20465.
The article has a link to the source code near the top of the article just
Angus Robertson - Magenta Systems Ltd wrote:
I'm writing simple console downloader and decided to use sync
operations in order to simplify structure. But I've found that
sync requests (HttpCli) do not use any timeout, so they may last
forever in case of error.
That's IMHO a bug.
Indeed,
But most components do have a timeout for sync methods, for
instance TSyncSmtpCli and TFtpClient.
Yes they have, but do they work properly when a send or receive
lasts longer then the timeout value?
I fixed the timeout in TSyncSmtpCli eight years ago, one of the first
changes I made to
Arno Garrels wrote:
Please guys, take a look at this fix for V7 and test it, anything
wrong with it?
Just noticed that it still lacks a timeout status.
--
Arno Garrels
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
Arno Garrels wrote
TWSocketCounter has been added to TWSocket in V7 with properties
ConnectTick, ConnectDT, LastAliveTick, LastRecvTick and LastSendTick.
Yes, I'm using it in my FTP class, but Start/StopTimer seem easier in my case
SZ wrote:
I think Arno and Francois is right about not making a
The problems seems to be edn.embarcadero.com (12.233.153.18) is sick
or off the air at the moment.
The domain responds to a Ping (average 173ms!) but none of the 3
browsers and 2 ISP combinations I have avalable here will download
anything from that address. Timout waiting for server, or
Server seems to be down indeed
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
Anton Sviridov wrote:
Arno Garrels wrote
Please guys, take a look at this fix for V7 and test it, anything
wrong with it?
It works, but I think Abort isn'tt a very good way to tell that there
was timeout...
Abort on timeout is commonly used in ICS.
and 404 even stranger. 404 means
The problems seems to be \edn.embarcadero.com\ (12.233.153.18) is sickor
off the air at the moment.
I've checked right now and it works perfectly.
I moved the file to my own server:
http://www.overbyte.be/arch/dump/trafficlight.zip
--
francois.pie...@overbyte.be
The author of the freeware
Any alternates (http://en.wikipedia.org/wiki/List_of_HTTP_status_codes)?
It's not a constant error AFAIK. IMO 408 was more confusing.
Yeah, that's why transport level stuff should be done in transport (socket)
classes :) We would have OnConnect(Request)Timeout or something like and no
mess
Anton Sviridov wrote:
Any alternates
(http://en.wikipedia.org/wiki/List_of_HTTP_status_codes)? It's not a
constant error AFAIK. IMO 408 was more confusing.
Yeah, that's why transport level stuff should be done in transport
(socket) classes :) We would have OnConnect(Request)Timeout or
Connect-timeouts are not the only possible ones.
Yes, I know, but connect ones are the most general and used by everyone,
because w/o connection there's nothing to do anyway.
If you need different timeout values for different states it has to be
implemented using a timer. We need to keep the
Anton Sviridov wrote:
Connect-timeouts are not the only possible ones.
Yes, I know, but connect ones are the most general and used by
everyone, because w/o connection there's nothing to do anyway.
If you need different timeout values for different states it has to
be implemented using a
13 matches
Mail list logo
