Just the Headers

re: Just the Headers

Alan Dean — Thu, 31 May 2007 16:10:03 GMT

"On that message you can put an HttpResponseMessageProperty that has SuppressEntityBody set to true. SuppressEntityBody produces equivalent messages to a one-way contract that have HTTP headers but no body contents."

aka: a HEAD request, rather than a GET

http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.4

Close Your Proxies

Nicholas Allen's Indigo Blog — Thu, 31 May 2007 20:01:04 GMT

Hey! Call Close on your client proxy objects once you're done using them! This is always a good idea,

re: Just the Headers

Nicholas Allen — Thu, 31 May 2007 21:55:31 GMT

The HTTP verb isn't really significant here because the client gets to pick the verb (could be anything) whereas the server is the one deciding not to send a body with the response. A lot of SOAP processing is done with POST instead of GET so switching to one-way doesn't affect that.

Interesting Finds: May 31, 2007

Jason Haley — Thu, 31 May 2007 22:32:10 GMT

re: Just the Headers

Juan Wajnerman — Sat, 02 Jun 2007 00:20:45 GMT

I think (if I understand well your approach) that you will loose the "fire-and-forget" behavior of one way operations. Am I correct?

Unless there is a way to return the empty message and continue with the execution flow somewhere in WCF stack. Is it possible?

re: Just the Headers

Nicholas Allen — Sat, 02 Jun 2007 06:00:12 GMT

Juan-

That's correct. By pushing the message processing up the stack, you lose the fire and forget behavior. There is a way though to send back an empty message but still continue on with execution. That way does require writing a channel. We have written such a OneWay channel- http://blogs.msdn.com/drnick/archive/2006/08/16/702174.aspx. The extensibility exists in the product for someone to write a similar channel or to modify the output of our OneWay channel to meet their needs.