You may run the ISAPI into the main thread, and having ICS code run into a 
worker thread with a message pump so that it can work asynchronously as 
usual. The ISAPI thread can then be blocked while ICS is doing his work and 
signal the main thread when done.
--
[EMAIL PROTECTED]
http://www.overbyte.be


----- Original Message ----- 
From: "Fastream Technologies" <[EMAIL PROTECTED]>
To: "ICS support mailing" <twsocket@elists.org>
Sent: Sunday, September 25, 2005 3:21 PM
Subject: Re: [twsocket] Converting Send() and Receive() to Sync


> ----- Original Message ----- 
> From: "Francois PIETTE" <[EMAIL PROTECTED]>
> To: "ICS support mailing" <twsocket@elists.org>
> Sent: Sunday, September 25, 2005 3:03 PM
> Subject: Re: [twsocket] Converting Send() and Receive() to Sync
>
>
>>> http://www.fastream.com/ics/WebConnection.pas
>>> I have been trying to convert a professional ISAPI 6.0 component to ICS.
>>> Scripts are now running but as for the internal logic of it, it needs
>>> sync
>>> read and write procedures. I have coded the attached unit for it but it
>>> gives access violations in InternalDataReady. I believe the problem is 
>>> in
>>> the WaitUntilReady function but not sure.
>>
>> Much better to avoid sync functions.
>
> For the ISAPI filter code to work, the thread needs to block. The easiest 
> to
> change part of the code is ICS because I know it the best.
>
>> You can probably rewrite part of the code in an async way.
>
> I do not understand what you mean. Could you take a look at the simple 
> code
> I wrote?
>
> Thanks,
>
> SZ
>
> -- 
> To unsubscribe or change your settings for TWSocket mailing list
> please goto http://www.elists.org/mailman/listinfo/twsocket
> Visit our website at http://www.overbyte.be 

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to