Hi James, On 12/5/06, James Mao <[EMAIL PROTECTED]> wrote:
I can not understand the conflicts between the current GET implementation and the one 'Multiple Endpoints on one Destination'. Do you mean, it can not be done with the current GET implementation? if that's the case, that's a problem. we need to fix this as soon as possible. Previously i thought the problem is just the isGET in several interceptors.
No, I was trying to make the point that the GET invocation requires different interceptors than the POST invocation currently and that we should consider separating those out into two Bindings with different sets of interceptors. How to understand HTTP GET is a separate binding from the SOAP binding?
You mean they have separate bindingFactory? But GET binding can not finish the job without the SOAP binding? and thus they must be pair presented in the chain? (Point 2: Supporting different bindings on the same URL) And if that's correct, then the SOAP binding you mean we can call the SOAP POST binding, because it only support POST. If you want to add GET function , you need another binding call SOAP GET binding. but the SOAP GET binding can not work properly alone, 'cause you have to add the SOAP POST binding. make sense?
When I made that comment I was thinking there could be logic in the SoapBindingFactory to determine if the soap binding being created was a GET binding or POST binding. This way there would be a binding for each one. And then we would have to select the appropriate binding at invocation time. Another way to do this would be to put the logic in the interceptor like I said in my message in the other thread. if GET, add GET interceptors, if POST add POST interceptors. Initially this interceptor would be the only one in the chain. - Dan -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
