[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Action item: Note about TextMessage from SOAP/JMS working group
As per my action item from this last conference call, here's a link to
the text which we just added around using TextMessage with JMS. http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?content-type=text/html;%20charset=utf-8#textmessage-considerations Since this is a reference into a working document CVS, I'm pasting the text below as well: 2.4.1 Considerations For Using TextMessage
Since
binary data needs to be encoded to be carried as text, SOAP attachments
via a In typical scenarios, using The in memory UTF-16 representation, coupled with base64 encoding of
an attachment, will consume much more memory than the equivalent As significant as the concerns around memory consumption may be, the
effects on network payload size are more difficult to predict. Since
the JMS API does not specify exactly how messages are handled, the
effects on network traffic are JMS provider-specific. A JMS provider
might be encoding a -Eric. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]