Re: osX PAP client timeout and Tickling
Re: osX PAP client timeout and Tickling
- Subject: Re: osX PAP client timeout and Tickling
- From: Akira Nagata <email@hidden>
- Date: Wed, 01 May 2002 02:07:48 +0900
Hi Laixin,
You are right.
Any lengthy job must cause timeout error if you use APIs of AppleTalk
framework.
This is a bug which Apple engineers might already know. They (who wrote
code for BSD) misunderstood about characteristic of tickle packet. I
exchanged some mails with Mr. Howard Ridenour of Apple in Janualy, then he
understood the problem, likely.
For now, you have to implement PAP handling code in your project directly,
and have the PostScript code to return some data during its job (if it will
take more than 2 minutes).
Cheers,
----------------------------
Akira Nagata
Technical Support
Yukos World Co., Ltd.
Tokyo Japan
mailto:email@hidden
on 02.4.30 6:29 AM, L. Liu at email@hidden wrote:
>
Rich Kubota wrote in message Re: [MacOS X] PAP connection closes in up to 120
>
sec.
>
> As per Inside AppleTalk, 2nd ed. page 10-9, PAP maintains a
>
> connection timer of 2 minutes. If after 2 minutes of no activity from
>
> one side of the connection, the connection is torn down.
>
>
>
Has OS X PAP interface implemented tickling itself or provided with function
>
like pap_tickle() life will be easier. Current pap_read() provided within
>
Darwin is a synchronous operation so it always blocks, thus any workaround
>
.using pap_read() to avoid timeout during length jobs would be difficult. Any
>
other ideas?
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.