I followed an interesting, timely thread on using SoapParameterStyle.Bare in your ASP.NET web services. I too am a big fan of the using Bare on the service method.
One additional point of note regarding some comments on compression in HTTP: HTTP compression really only works on responses, and if you move to WS-Security for message-level encryption using, say, WSE, then compression won't buy you much, because the encrypted contents are sufficiently random enough to not compress worth a doody. Reasonably sized, xml data encrypts compresses (thanks for catching the typo, Todd) quite nicely, though. You can try it out for various size files using the following simple method. Go to the web. Download several html pages based on their size. Compress each of them to a zip file using your favorite compression tool. Compare the sizes. You typcially don't want to compress the messages below a certain threshold, but the rest of them, you do.
In general, you would prefer to compress before you encrypt because the encryption cost is usually higher. Morty has an experimental compression filter for WSE, and he discusses the issue further based on his experience implementing it. One problem with compressing ws-security afflicted content is that there is a really good chance that the size of the message due to the security info in the headers, etc is far, far larger than the message you are sending, and you might not be getting much benefit from the compression because your message is sufficiently small. If you are dealing with coarse-grained, document-oriented business services, you might have some meat worth the compression. Of course, there doesn't appear to be anything more than the gleam in a couple of people's eye's at this point regarding compression in WSE.
Via Steve to several posts by Tim leading to some posts and comments by Craig, Richard, and Cleve. No, I am not actually on a first name basis with any of them.
Posted by: Craig | 2004.07.01 at 11:42 AM
Posted by: Steve Maine | 2004.07.01 at 09:13 PM