- From: Mark Nottingham <mnot@mnot.net>
- Date: Wed, 27 Apr 2005 11:35:22 -0700
- To: xml-dist-app@w3.org
The SOAP in BEEP binding document is undergoing revision in the IETF; http://ftp.ietf.org/internet-drafts/draft-mrose-rfc3288bis-01.txt One of the things that I noticed during a quick look-over is that it now supports XOP; I found this section especially interesting; > As stated in Section 4 > of XOP [8], XOP may be used with diverse packaging mechanisms. When > an implementation of BEEP in SOAP does support MTOM/XOP, it SHOULD > support the MIME Multipart/Related XOP Package format, and MAY > support others. Additional formats could in future include XOP > package formats specific to BEEP (For example, sending the > attachments on a different channel to the SOAP channel, which would > avoid searching for the MIME boundary tags and allows lazy delivery > of attachments - delivering them only when really needed.) Cheers, -- Mark Nottingham http://www.mnot.net/
Received on Wednesday, 27 April 2005 18:35:36 UTC