Hi All, How is a WS-Routing Intermediary best implemented, as a Web Service or as a Soap Extension or as a Http Handler How is a WS-Routing Ultimate Receiver best implemented, as a Web Service or as a Soap Extension or as a Http Handler.
A WS-Routing Intermediary can act as an intermediary for a specific web service only or it can be an intermediary for any number arbitrarty web services ( not known at the time of implemntation ). Suppose i want a loggger WS-Routing Intermediary written do i have to write a separate logger for each and every web service (i.e.) one for echoString, one for echoInt etc. or the same intermediary will do for echoString, echoInt and any other arbitrary service not known at time the Intermediary is implemented. If the same intermediary can be used how to forward a call to a unknown web service how can this be done in .NET code only the endpoint is know. Sendhil Kumar R. MS .NET Developer Ph: 080-6610330 Extn: 3193 http://www.sonata-software.com ********************************************************************* Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. ********************************************************************* You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
