Re: How to set the expiration date of an applet downloaded via a Cocoon pipeline?

[Joerg Heinicke]

It seems to interpret the expires="-1". You can set this value by adding 
a parameter to your map:read:

<map:read mime-type="binary/jar" src="context://app1/lib/{1}">
  <map:parameter name="expires" value="86400000"/>
</map:read>
It's in seconds.

Joerg

On 28.10.2003 18:48, jcplerm wrote:

I am trying to serve an applet jar via Cocoon to a Java Plugin client
(JDK 1.4.2) and I am having trouble making the Plugin caching
mechanism work.
The jar file is accessed via the following pipeline:

<map:match pattern="lib/*">
  <map:read mime-type="binary/jar" src="context://app1/lib/{1}"/>
</map:match>
I set the "cache_archive" and "cache_version" attributes of the
"<OBJECT>" tag according to Sun's web page: 
http://java.sun.com/j2se/1.4.1/docs/guide/plugin/developer_guide/applet_caching.html

But the applet jar is always downloaded, even if the version in the
client cache is exactly the same as on the server.
I noticed on the Java Plugin's control panel that the expiration date
on the cached file is set to "12/31/69", which might be "1969", thus
resulting in the jar never being cached and always downloaded from
the server.
Therefore my question is: how can I explicitly set the expiration
date of a jar file downloaded via a Cocoon pipeline as listed above?
Thanks,

jlerm


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]