As some of you may know, we are moving the configuration and resource
handling strategy in the cache towards one based uniformly in URL,
instead of having a mixed File/URL strategy.
This move has advantages on its own:
one could use a servlet to serve user psml "files"
a dedicated server could manage the disk cache, serving remote URLs to
the farm of user servers through HTTP
feeds could be generated dynamically, again from a "content server", to
the view stations ...
...
in addition, the URL handling of java is much more uniform than the
handling of files (drive letters, path separators, ...)
Now, when helping to implement this scheme, I have found a couple of
places where I have problems with this, related with the need of writing
back to these resources:
jetspeed-content. It need a file to write, or else it need to be able to
"PUT", or "POST" back content.
The problem will appear again in what is related to customising, as the
user will need to save back th modified psml resource.
The problem I have currently is:
How do I give the developer a chance to save back a resource?
The obvious API change would be to add some new API to the disk cache:
isWritable()
getOutputStream()
setData()
Also, how do we implement this scheme? I would resist to go back to redo
the mapping between resources and files, as we have already discarded
this mapping by the problems in maintenance and configuration it has.
The ideal would be to implement writable resources via a servlet, that
would take them using HTTP PUT. The servlet would be a pluggable
resource, having the responsibility of storing and delivering "local"
writable resources, be it via database, memory, file, whatever. We could
implement a reference file writer. I don't know how would the system
know that a resource is writable, apart from having a
"writable.url.prefixes" array property.
Any ideas?
Regards,
Santiago
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
