http://winterdom.com/2007/02/urisandwcftransportchannels by dæmons be driven Tue, 16 Mar 2010 00:20:05 +0000 http://wordpress.org/?v=2.9.2 hourly 1 http://winterdom.com/2007/02/urisandwcftransportchannels/comment-page-1#comment-694 Scott Seely Wed, 21 Feb 2007 08:36:20 +0000 http://winterdom.com/2007/02/urisandwcftransportchannels#comment-694 The address element can take a set of extra headers-- see EndpointAddress.Headers. These headers can also be passed in as part of the config object model. This feature exists to handle scenarios like yours. The URI should contain enough information to hit the endpoint. What I'm trying to get at is that you don't need to encode everything in the URI-- you have headers as well. As for asymmetry in the URI scheme, what you need to do is tell any clients, via policy and WSDL, how to connect to your endpoint. So long as you can express that asymettry in a way that the client can work with it with no ill effects, you should be fine. The address element can take a set of extra headers– see EndpointAddress.Headers. These headers can also be passed in as part of the config object model. This feature exists to handle scenarios like yours. The URI should contain enough information to hit the endpoint.
What I’m trying to get at is that you don’t need to encode everything in the URI– you have headers as well. As for asymmetry in the URI scheme, what you need to do is tell any clients, via policy and WSDL, how to connect to your endpoint. So long as you can express that asymettry in a way that the client can work with it with no ill effects, you should be fine.

]]>