Hi Calvin,
I think it's dangerous to implement the way what you proposed.
The WebServices are *NOT* static contents, so your client will
get some wrong message ( i.e. old message cached by various
network devices including proxys ) if you use the mechanism.
Is it acceptable for you ? I wouldn't prefer the methods if so.
In this situation, do you still want to have a cache for WS ?
What's the root problems in your system ? I mean that do you
have any actual troubles ?
Regards,
Toshiyuki Kimura <[EMAIL PROTECTED]>
R&D Headquarters
NTT DATA Corp.
-----Original Message-----
From: Calvin Smith [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 08, 2003 2:11 AM
To: [EMAIL PROTECTED]
Subject: RE: axis and caching
Each time a repsonse is sent from axis it needs these two lines in the HTTP
header:
Cache-Control: no-cache
Pragma: no-cache
This is so that the various gateways/routers/vpn servers/whatever else knows
not to cache the result of a soap message
NOTE: these lines are included in the client, so only the server(servlet?)
needs fixing.
----Original Message Follows----
Hi Calvin,
I guess that the current AXIS doesn't have the optoin
for caching control. What's your problems ?
I might provide a solution depends on your condition.
Regards,
Toshiyuki Kimura <[EMAIL PROTECTED]>
R&D Headquarters
NTT DATA Corp.
-----Original Message-----
From: Calvin Smith [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 07, 2003 5:21 AM
To: [EMAIL PROTECTED]
Subject: axis and caching
I'm testing with axis 1.0 and have noticed that axis does not specify that
the soap response is not cachable, which causes me some problems. Is there
an option for axis to suppy the caching control in the response?
_________________________________________________________________
The new MSN 8 is here: Try it free* for 2 months
http://join.msn.com/?page=dept/dialup
