>We also discussed that a server MAY keep a list of clients that are
trying
>to connect in a "queue", and then serve each one one at a time. Then
the
>client doesn't receive an error (except if the "queue" is filled).
This
>gives the end-user a much happier experience.
Consider the scenario:
An IPP Client tries to print a job to an IPP server. A non-spooling
HTTP/IPP server received TCP SYN pkt on port 80
from the IPP
client, responded back with a TCP SYN-ACK pkt, and then received
an ACK pkt from the IPP client. At this point, the HTTP/IPP
server does not know whether the next pkt is going to be an IPP request
or a simple HTTP operation for its embedded web.
Next comes the first HTTP POST
pkt with IPP header and IPP data. However, at this time, the
HTTP/IPP server realized that another IPP job is in the process
of printing. What will the IPP server do? if we follow the first
recommendation, it will immediately send a 0x0502 IPP status
to indicate that the service is temporarily. However, if we follow the
second recommendation, should the non-spooling IPP server just sit
idle and not respond to the new HTTP POST operation?
Thanks,
PB
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com