HI Chad Sorry, didn't get to this earlier. When we started looking at what should go in the various parts of the Tuscany message we were trying to avoid putting protocol specific data in there. We had framework that allowed the binding itself to extract the required info from the protocol specific data and put that in the Tuscany message.
Then that all changed and we switched tack to go with the idea of wireFormat and a binding wire [1]. This is really handy as it provides a consistent mechanism for accessing binding specific data. However we haven't got round to upgrading the web services binding to adopt this new framework (the JMS biding and HTTP binding have it) So I would say go ahead and create the patch and we can discuss. I'll take a look at binding.ws and remind myself what that is actually doing at the moment. Regards Simon [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Request+Response+Binding
