Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Archive
ASP .Net
ASP .Net Web Services
SOAP Message sender info
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
Reply to thread
Message
[QUOTE="John Saunders, post: 4324479"] None of this will happen by magic. You'll have to 1) Determine, at the site of the web service call, how to identify the application making the call. This could be as simple as identifying the host name and the root of the web application 2) Send that identifying information in the web service call 3) Receive that information in the web service and log it You could put that information into a SOAP header, and it could be logged on the other side. Remote callers to your web service could do the same. On the other hand, since it's not going to be trivial to do this, and not easy to do it well, you might consider deferring this task until you're more experienced. Perhaps after you've had occasion to use SOAP Headers for more "normal" purposes, you could revisit this requirement in the light of your successful use of SOAP Headers. John [/QUOTE]
Verification
Post reply
Forums
Archive
Archive
ASP .Net
ASP .Net Web Services
SOAP Message sender info
Top