Re: Jigsaw's cache mecanism

Yves Lafon,

thank you very much for your quick answer.

I still have some questions...
 
> > Since  w3c.www.protocol.http.cache.CacheFilter class doesn't seem to
be
> > a filter, it cannot work coupled to a resource, does it? In this case,
> > why does this class have the ingoingFilter e outgoingFilter methods?
> 
> It is a filter! But a client-side one, you may also notice an exception 
> filter which is used in ProxyDispatcher, for example. (See the "Client 
> Side Components" part of the documentation).

Ok. I thought it was not a filter since all filters are  defined
as a subclass w3c.jigsaw.resources.ResourceFilter as stated in 
the filter tutorial.
 
> > Is it possible to use the proxy coupled if the cache mecanism
disabled?
> > How to disable it?
> 
> By default, the proxy doesn't use the cache

In case, the proxy use the cache by default. I didn't change the original
set up but my Jigsaw/Jigsaw/config/cache diretory is full of cached.*
archives.
 
> to use the cache, or ICP, or 
> ProxyDipatcher (or any hand-made client-side filter), you should add it 
> from the Proxy property sheet, or set directly the 
> w3c.www.protocol.http.filters property in the server props file (it is 
> better to add the filters via the configuration interface).

I tried to do it today but I got the following page:

Failed to create and attach filter to target:
w3c.www.protocol.http.cache.CacheFilter

and the message in the command line:

...
Jigsaw[1.0alpha5]: serving at http://machine:8001/
java.lang.ClassCastException: w3c.www.protocol.http.cache.CacheFilter
        at
w3c.jigsaw.formedit.AddFilterHandler.notifyEndProcessing(FilteredResourceEditor.java)
        at w3c.jigsaw.forms.FormCardResource.handle(FormCardResource.java)
        at w3c.jigsaw.forms.PostableResource.post(PostableResource.java)
        at w3c.jigsaw.resources.HTTPResource.dispatch(HTTPResource.java)
        at w3c.jigsaw.resources.HTTPResource.perform(HTTPResource.java)
        at w3c.jigsaw.http.httpd.perform(httpd.java)
        at w3c.jigsaw.http.Client.processRequest(Client.java)
        at w3c.jigsaw.http.Client.startConnection(Client.java)
        at w3c.jigsaw.http.socket.SocketClient.run(SocketClient.java)
        at w3c.util.CachedThread.run(ThreadCache.java)


To be clearer, let me explain what I am trying to do with Jigsaw.
I'd like to use the ProcessFilter coupled to the proxy. I need to know
how to programm it in order to guarantee the caching will be done
ONLY after the execution of the content of the ProcessFilter COMMAND
attribute. 

Thank you, Julianne.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Julianne Freire Pepeu    Departamento de Informatica, UFPE
jfsp@di.ufpe.br          http://www.di.ufpe.br/~jfsp



>       /\        E tae koe ki Aotearoa kaua e whawhai; e u koe ki uta,
>   /\ /  \       kei mahi ki tai ki Tu, puhia he angina; e mau ki tai
>  /  \    \/\    ki Noho, he huhu, he pepe, he hanehane.
> /    \   /  \        - Yves Lafon - W3C / INRIA - ylafon@w3.org -
> 
> 
>

Received on Monday, 30 June 1997 16:30:27 UTC