For you, here is the list of events called with fast HEADs in order:

 - OnHeaderData // header data here is "0".
- OnHeaderEnd
- OnSessionClosed
- OnHeaderData // header correct
- OnHeaderEnd // document could not be retrieved since connection closed
Regards,

SZ
On Wed, May 28, 2008 at 7:58 PM, Fastream Technologies <[EMAIL PROTECTED]>
wrote:

> I just tried to Post a message from onrequestdone and it did not work
> either. It is irrelevant.
>
> SZ
>
>   On Wed, May 28, 2008 at 7:41 PM, Fastream Technologies <
> [EMAIL PROTECTED]> wrote:
>
>>  On Wed, May 28, 2008 at 7:38 PM, Arno Garrels <[EMAIL PROTECTED]>
>> wrote:
>>
>>> Fastream Technologies wrote:
>>> > Yes of course we use Async. I noticed this behavior is followed by
>>> > onsessionclosed!
>>>
>>> You said that you call the subsequent GET-command from OnRequestDone.
>>> Do you call GET directly, or do you post a custom message so that the
>>> GET would be issued delayed?
>>>
>>> I simply called GetAsync() from OnRequestDone of HEAD. I thought this was
>> ok since OnRequestDone was called from a posted event.
>>
>> Regards,
>>
>> SZ
>>
>
>
-- 
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

Reply via email to