|
From: Steven H. <sh...@te...> - 2005-10-03 08:48:35
|
According to what documentation I have handy with me, binary information in a soap message is base 64 encoded - which is logical, you have to ensure that the binary data doesn't break the xml envelope its transmitted in. Since Base64 encoded takes up about 33% more space than the orginal data I'd say that explains the timing differences. If you are doing the messaging over SSL, then you'll also be taking a bandwidth hit for that (quite apart from the encryption computational overhead) -----Original Message----- From: ebx...@li... [mailto:ebx...@li...] On Behalf Of R. van Kuijk (Ronald) Sent: Friday, 30 September 2005 5:09 PM To: ebx...@li... Subject: RE: [ebxmlms-general] Text vs. binary payload I agree, but is the difference really in the 7 or 8 bit? Or is it because binary data is often base64 encoded before transmission? (or is that the 'CRC' as you put it ;-)) Ronald -----Oorspronkelijk bericht----- Van: ebx...@li... [mailto:ebx...@li...] Namens David Webber (XML) Verzonden: donderdag 29 september 2005 4:19 Aan: ebx...@li... Onderwerp: Re: [ebxmlms-general] Text vs. binary payload Patrick, It's much more likely to be a behaviour of the router and the network hardware. 7bit ASCII goes faster over any network infrastructure. 8bit binary has much more CRC and transmission overhead (upto 30% larger than the actual bit count sent). So my guess is - if the binary takes 30% longer - its the network overhead. DW ----- Original Message ----- From: "Patrick Yee" <kc...@ce...> To: <ebx...@li...> Sent: Wednesday, September 28, 2005 4:19 AM Subject: Re: [ebxmlms-general] Text vs. binary payload > Sorry we don't have an explanation on that. Actually we treat text > content and binary content equally, they are all garbage-in garbage-out. > You can try to configure Content-Transfer-Encoding settings (like > base64) in msh.properties.xml. It makes the Hermes handle the payload > using some encoding algorithms. Maybe you can find out some clues from that. > > Regards, -Patrick > > > em...@og... wrote: > > > > > It seems that it takes a longer time to send a binary attachment when > > compared with an attachment of text content. Any one has this > > experience and is it the normal behaviour of the ebMS Implementation. > > > > Thanks! > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > ebxmlms-general mailing list > ebx...@li... > https://lists.sourceforge.net/lists/listinfo/ebxmlms-general > ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ ebxmlms-general mailing list ebx...@li... https://lists.sourceforge.net/lists/listinfo/ebxmlms-general ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ ebxmlms-general mailing list ebx...@li... https://lists.sourceforge.net/lists/listinfo/ebxmlms-general |