> I try to avoid the low level winsock stuff, but I do know that
> TIcsBufferHandler is used to store
> everything before it is sent, each buffer is 1460 bytes (TCP packet size).
> So your application would be allocating 13,700 linked buffer pages before
> anything was sent, which is
> quite an
I have a simple Delphi 7 application that reads data from a remote host. I
want the application to stay ALIVE and continue to wait for data even when
there is no messages from the host. Here are the setting of my component,
flush Timeout = 60, KeepAliveInterval = 1000, KeepAliveOnOff =
wsK
On Wednesday, July 03, 2013 12:04 PM [GMT+1=CET],
Tobias Rapp wrote:
> As the last changes in this area have been made by Arno I have
> included him in CC of this mail.
Huh? It looks like Angus added hcSendData to the THttpConnectionState.
I must admit that I have not yet updated my own webserver
> Looking at TWSocket code, I don't see why one could not send 20MB
> in one chunk
I try to avoid the low level winsock stuff, but I do know that
TIcsBufferHandler is used to store everything before it is sent, each
buffer is 1460 bytes (TCP packet size).
So your application would be allocating
I understand your point, in fact I've already refactored my server with
OnDataSent. Yet I am concerned by the fact that this large block was not
going through, something for which I have no explanation. In fact in some
cases I had only about 32KB transferred before things would stop working.
Loo
> I've used TWSocket/TWSocketServer to build client/server
> successfully in the past. Now I have one where I need to send a
> 20MB block of data from server to client.
> it is my understanding that TWSocket is built to handle this
> situation
Not sure why you expect to send a single block 20MB
Hello,
I've used TWSocket/TWSocketServer to build client/server successfully in the
past. Now I have one where I need to send a 20MB block of data from server
to client. Depending on the computer where the server is running and where
the client is running, my block of data does not always get se
> On a second look the existing "hcRequest" state seems to be the
> state that I
> am searching for: the server socket is waiting for new requests. My
> question is, why is the state not automatically reset after
> "hcSendData" back to "hcRequest"?
> As the last changes in this area have been mad
Angus Robertson - Magenta Systems Ltd wrote:
> > should I add a new connection state "hcIdle" for it
>
> Yes, a new THttpConnectionState makes sense, but do check the code
> carefully to see what else is dependent upon it.
On a second look the existing "hcRequest" state seems to be the state th
