Larry Masinter wrote:
>> If you use XML for the protocol mapping and yet want to get
> file data in, you might consider a protocol mapping which separates
> the print data stream from the print protocol using MIME
> multipart, e.g., "multipart/related" where the print protocol
> elements are in an XML data structure, and the binary data streams
> are encoded appropriately just with their MIME media designations
> (application/postscript, etc.).
This seemed like a nice approach to me as well. In fact, I so much
as raised it as a suggestion at the last IPP conference call (only
I being a MIME neophyte suggested "multipart/mixed"; your suggestion
sounds a lot better to me). However, my suggestion was immediately
shouted down, as "this issue had already been discussed in the past,
and a decision made".
Well, as we are re-visiting the protocol encoding at this point, I
would like to have this decision re-considered as well. It seems
like a multipart MIME message, with the protocol and data in separate
parts would be a natural solution.
...walker
--
Jim Walker <walker at dazel.com>
System Architect/DAZEL Wizard
DAZEL Corporation, Austin, TX