Francois PIETTE wrote:
1) Command Open succeeds.
2) After the server received command User it closes the connection
(FIN/ACK).
3) OnSessionClosed triggers with ErrCode 0.
4) OnRequestDone triggers with ErrCode 0 and the status code from
previous request.
Would you agree that is a bug?
Markus Humm wrote:
My application now has to tell the communication part (means the
server side of the TWSocket connection) to shut down. it sends him a
binary shutdown command and after a short time the client does a
shutdown(1) on the socket.
There's most likely something wrong in your
Do you see anything obviously wrong in this fix?
I Don't.
GetWinsockOrProxyErrorStr(ErrCode); // == New function, not related to
this fix
I would name this function GetErrorMsgFromErrorCode since it is a general
translation from an error number to a message. Probably the implementation
Francois PIETTE wrote:
GetWinsockOrProxyErrorStr(ErrCode); // == New function, not
related to this fix
I would name this function GetErrorMsgFromErrorCode since it is a
general translation from an error number to a message.
IMO, from the name it should be clear what range of error
GetWinsockOrProxyErrorStr(ErrCode); // == New function, not
related to this fix
I would name this function GetErrorMsgFromErrorCode since it is a
general translation from an error number to a message.
IMO, from the name it should be clear what range of error numbers
are expected to be
Hi,
I am using the TWSocket component as client and server . Server is sending
data regularly @ 3000 bytes/seconds . But client is disconnnect after
some time ( 2 or ,3 or 4 minutes ) frequently . There is no ping break
between them .why it is happening.
--
To unsubscribe or change your
I am using the TWSocket component as client and server . Server is sending
data regularly @ 3000 bytes/seconds . But client is disconnnect after
some time ( 2 or ,3 or 4 minutes ) frequently . There is no ping break
between them .why it is happening.
Assuming you are using TCP...
Maybe bad
Server some time shows the following exception
not connected (#10057 in Send)
On Sat, Feb 12, 2011 at 9:23 PM, Francois PIETTE
francois.pie...@skynet.bewrote:
I am using the TWSocket component as client and server . Server is
sending
data regularly @ 3000 bytes/seconds . But client is
Server some time shows the following exception
not connected (#10057 in Send)
This happen when you try to send something after the client is disconnected.
--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite
Hi,
I've been working on Twitter's OAuth implementation, for which I'm using
THttpCli. There are various ways to do this, one of which is adding some
Auth data in the http headers and not including the parameters int he GET
call. However, there's no option in httpcli to manually modify the
On 12-02-2011 22:31, brian - wrote:
there's no option in httpcli to manually modify the headers
before a request
You can do it from the OnBeforeHeaderSend event.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto
Oh yeah, dunno why I thought that was read only same effect anyway, the
output headers are the same and still OAuth fails. Maybe something to do
with the way httpcli sends the headers?
On Sat, Feb 12, 2011 at 11:42 PM, RTT p...@sapo.pt wrote:
On 12-02-2011 22:31, brian - wrote:
there's no
On 12-02-2011 22:31, brian - wrote:
Authorization: OAuth oauth_callback=oob, realm=,
oauth_nonce=5B2407849960FC2B4EC23007EA63E8ED,
oauth_timestamp=1297549627, oauth_consumer_key=5BZYtiAzGvQTL0ZEhAn45w,
oauth_signature_method=HMAC-SHA1, oauth_version=1.0,
only 1 line
SHeader := 'Authorization: OAuth oauth_callback=oob, realm=,
oauth_nonce=' + nonce +
', oauth_timestamp=' + tstamp + ', oauth_consumer_key=' +
ConsumerKey +
', oauth_signature_method=HMAC-SHA1, oauth_version=1.0,
oauth_signature=' +
Hello Francois,
OK, after another series of tests it turned out that I have no idea
what the problem is. The user could find out that:
- using a passive connection to transfer any file of a certain size
(maybe larger than 38Mb but maybe 37.Mb) causes a failure under
unknown
That is the real problem why socket connection is disconnect. automatically
On Sun, Feb 13, 2011 at 12:48 AM, Francois PIETTE francois.pie...@skynet.be
wrote:
Server some time shows the following exception
not connected (#10057 in Send)
This happen when you try to send something after the
That is the real problem why socket connection is disconnect.
automatically
Please read again my first answer and answer all the questions I aksed and
follow the advice I gave.
By the way, is this problem related to the previous problem you asked
questions for ?
If yes, please answer the
OK, after another series of tests it turned out that I have no idea
what the problem is. The user could find out that:
- using a passive connection to transfer any file of a certain size
(maybe larger than 38Mb but maybe 37.Mb) causes a failure under
unknown conditions (the ftp
18 matches
Mail list logo
