Re: OpenTransport Timeouts?
Re: OpenTransport Timeouts?
- Subject: Re: OpenTransport Timeouts?
- From: "Duane Murphy" <email@hidden>
- Date: Thu, 10 Nov 2005 07:16:10 -0800
--- At Thu, 10 Nov 2005 14:59:58 +0000, Quinn wrote:
>At 22:27 -0800 9/11/05, Duane Murphy wrote:
>>I know this is ancient history [...]
>
>Apple archaeologist at your service (-;
Excellent.
>>Is there a way to control or detect timeouts for simple OpenTransport
>>TCP endpoints? I'm using synchronous blocking endpoints with a notifier
>>and sync idle events (aka OTSimpleDownloadHTTP).
>>
>>Is there a way to control the timeout on the connection? That is detect
>>if there has not been any response for some period of time?
>
>If you're running on traditional Mac OS, OT supports timeout options.
>However, these were never officially documented and aren't
>implemented by the Mac OS X OT compatibility library. Let me know if
>this is interesting and I can dig up the details.
This is only for traditional Mac OS. There is a separate implementation
for OS X that uses sockets.
If it's not to complicated or difficult, I wouldn't mind seeing these.
>Otherwise, your best option (at least in this case) is to have your
>notifier check for the timeout and call OTCancelSynchronousCalls on
>the endpoint. This will get you out of the sync/blocking call
>(although it does have the side effect of killing the endpoint, so
>use this technique if a timeout is fatal).
Until, I hear from you, I'll give this a try.
><obligation> Stop using Open Transport! </obligation> (-:
We are. This is for traditional Mac OS.
Thanks,
...Duane
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden