I'm OK with the clarification. You are basically just adding the fact that
the sniffing method is implementation dependent... right?
More important, to me, is to encourage that no client ever use
application/octet-string when they are aware of and capable of indicating
the correct document format in mimeMediaType!
IBM Printing Systems
I searched both the Model and the Implementer's Guide and there isn't
anything that explains what "auto-sensing" is.
So, ok to add the following clarification to the [ipp-mod] document in
using an implementation-dependent method that examines some number of
octets of the document data
so that it reads:
184.108.40.206 Application/octet-stream -- Auto-Sensing the document format
One special type is 'application/octet-stream'. If the Printer object
supports this value, the Printer object MUST be capable of auto-sensing
format of the document data using an implementation-dependent method that
examines some number of octets of the document data, either as part of the
create operation and/or at document processing time.
Or should we put something similar in the Implementer's Guide, instead?
It can usually tell from the first few bytes of the file. For example,
PostScript files start with %!PS and PDF files start with %PDF. Gif files
start with GIF89 and so on.
I have a doubt in the "document-format" attribute that the client
optionally specifies in the request..(according to IPP/1.1 draft)
The draft says that if theclient supplies this attribute and its value
'application/octet-stream' then the server needs to aut-sense the
Can anyone explain me how does this autosensing happens.......
How actually will the Printer Object perform this task...
This archive was generated by hypermail 2b29 : Tue Mar 28 2000 - 12:43:36 EST