I'm not sure what you mean by "premature response", but the client certainly needs to be prepared to accept responses prior to completion of transmission of the request. IPP recommends sending a response (failure OR success) as soon the request attributes have been processed (without waiting for document data).
Also "[An HTTP/1.1] client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100 (Continue) status message."
> Basically, I'm planning on seeing broken IPP servers and/or clients
> and don't want *our* software to break because of it.
> > ...
> > I don't see why keeping the connection open means that you can't
> > send the error response until after all data has been received.
> > That seems inefficient to me. Ideally you'd want to send the error
> > response ASAP to get the client to cease transmitting the body.
> > ...
> Again, I'm not disagreeing here, I'm just being realistic about the
> clients that'll be out there.
> Michael Sweet, Easy Software Products firstname.lastname@example.org
> Printing Software for UNIX http://www.easysw.com
See the original message at http://www.egroups.com/list/ipp/?start=4971