Re: PAP not working in X
Re: PAP not working in X
- Subject: Re: PAP not working in X
- From: Will <email@hidden>
- Date: Thu, 18 Apr 2002 14:14:44 -0500
Hmmmm, well does anyone know of an example of using the pap_read
and pap_write functions? I have one called callAT and that is what I
have been using but it is also the code with the problem, I have gone
through this file and bare bones created another file that is much
cleaner and just has the 4 pap methods open, write, read, and close. I
tried with that and it still hangs on the 5th write. I am about to
check the packets between the computer and the printer as I noticed the
lock up leaves the printer in a waiting state therefore I am guessing at
least part of the 5th packet is getting over there, I just have a
feeling it is going to be corrupt.
Also, I checked the Apple example code at the web site and couldn't
find an example of a client using PAP just PAP servers anyone got an
example of a PAP client for OS X?
On Thursday, April 18, 2002, at 12:29 PM, Rich Kubota wrote:
At 8:51 AM -0500 4/18/02, Will wrote:
Hello,
I'm not sure if this is a Carbon problem or a PAP(networking)
problem but I'll ask here since the Carbon group didn't seem to have
any ideas. I am using PAP in OS X to query a printer and have no
problem opening the connection, making one query, then reading the
answer, and then closing the connection, then later on when I need it
again making the PAP connection, sending the message, reading the
answer...and on it goes. Problem I am having is when I open the PAP
connection and write/read more than 4 times on the same PAP connection
it locks up on the 5th attempt to write. Anyone know about this
being a problem or bug? Am I supposed to be using PAP or is Apple
moving on to another API for talking to the printer? If PAP is still
supported should I be using a newer API than the one with pap_read and
pap_write?
Thanks
Will
Hi will,
I've not heard of this problem, but as I recall, I had performed a test
using the pap_read and pap_write calls in which I established separate
connections with the printer for more than 4 times. In my case, I had
launched the application multiple times. This is slightly different
than opening and closing the connection multiple times from the same
instance of an application.
In your case, the first thing I would do is look at the packets to see
what network activity is on the wire between your client application
and the printer. You may well have found a bug, however, this is not
one that I'm aware. Others might recall these symptoms and provide
additional comment.
As for what Apple does, the Print Center application uses the BSD pap
and atp api's whose source code is available in Darwin.
-- Sincerely,
Rich Kubota
email@hidden
(408) 974-6212
_______________________________________________
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.