Routing and Timestamps

When we looked at timestamps in the previous chapter, we mentioned that routing also affects the timestamps that are generated. When we route requests to Web services using any of the routing methods discussed in this chapter, we also record the timestamp details for the router in a <wsu:received> element in the timestamp header.

Thankfully, the Timestamp filters handle this automatically; whenever we pass through a router, a Received element is added to the timestamp header containing the time the message was received as well as how long the message was delayed by the router.

If we turn on the Timestamp filters for our Web services, every router that is passed through on the way to the final destination will have a <wsu:Received> element added to the timestamp header. As an example, the following is the timestamp header that is received at TellMe.asmx when we pass the message through RouterA.asmx:

<wsu:Timestamp xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility">   <wsu:Created>2003-02-26T22:01:58Z</wsu:Created>    <wsu:Expires>2003-02-26T22:06:58Z</wsu:Expires>    <wsu:Received     Actor="http://localhost/wscr/14/RouterA.asmx"     Delay="30234">     2003-02-26T22:02:08Z   </wsu:Received>  </wsu:Timestamp>