Re: SOAP Response caching

But the ttl approach requires clock synch between clients,
intermediaries and servers - how realistic is that?

Is anybody actually using this approach for caching?  Based on what
rules?  Are you piggybacking referral headers with messages or making
referral queries?

Jim

> -----Original Message-----
> From: Discussion of implementing SOAP applications today
> [mailto:[email protected]] On Behalf Of Marc Mercuri
> Sent: Wednesday, October 16, 2002 10:34 AM
> To: [email protected]
> Subject: Re: [SOAP] SOAP Response caching
>
> Jim,
> This is covered in the WS-Referral spec. You can specify a ttl (Time
To
> Live) that specifies a lifetime. Also, a referrer can invalidate a
> previously given referral.
>
> http://msdn.microsoft.com/library/default.asp?url=/library/en-
> us/dnglobspec/
> html/ws-referral.asp
>
> Marc
>
> Marc Mercuri
> VP, Software Development
> Gazelle Systems, Inc.
> 377 Elliot St.
> Newton Upper Falls, MA. 02464
> p 617.630.8600 ext236
> f 617.630.8424
> e [email protected]
>
>
> -----Original Message-----
> From: Jim Murphy [mailto:[email protected]]
> Sent: Wednesday, October 16, 2002 11:00 AM
> To: [email protected]
> Subject: Re: [SOAP] SOAP Response caching
>
> Anyone have strong feelings about how this is done?  A quick scan of
the
> WS-Routing spec yields a mention of response caching/short circuiting
> but explicitly makes no mention of how the intermediary is supposed to
> make that decision.
>
> Is anyone working of SOAP cache control headers?
>
> Jim
>
> You can read messages from the SOAP archive, unsubscribe from SOAP, or
> subscribe to other
> DevelopMentor lists at http://discuss.develop.com.
>
> You can read messages from the SOAP archive, unsubscribe from SOAP, or
> subscribe to other
> DevelopMentor lists at http://discuss.develop.com.

You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other
DevelopMentor lists at http://discuss.develop.com.