XML Logging: Difference between revisions
m
→Web Service XML Logging
m (→Step 4) |
|||
| Line 26: | Line 26: | ||
There is a very real difficulty regarding accessing the XML which is passed it a VDF Web Service (at least so far as revisions up to VDF 12.1 are concerned). The problem is that the original XML is nowhere available to the VDF program. One possible solution would be to employ some kind of HTTP proxy on the server involved, which would receive the XML (actually the HTTP within which the XML is wrapped) ''before'' it reached IIS, log that, then pass it on to IIS. However here we are going to concern ourselves only with the best that can be managed from within the VDF programming environment at the moment (November 2007). | There is a very real difficulty regarding accessing the XML which is passed it a VDF Web Service (at least so far as revisions up to VDF 12.1 are concerned). The problem is that the original XML is nowhere available to the VDF program. One possible solution would be to employ some kind of HTTP proxy on the server involved, which would receive the XML (actually the HTTP within which the XML is wrapped) ''before'' it reached IIS, log that, then pass it on to IIS. However here we are going to concern ourselves only with the best that can be managed from within the VDF programming environment at the moment (November 2007). | ||
The trick is to make use of a ''client'' of you service ''within'' the service itself. This in turn makes doing it a multi-stage process, since one can only create a client once the service is published and | The trick is to make use of a ''client'' of you service ''within'' the service itself. This in turn makes doing it a multi-stage process, since one can only create a client once the service is published and accessible. | ||
====Step 1==== | ====Step 1==== | ||