Thorsten Scherler wrote:
El mié, 15-03-2006 a las 07:02 -0500, Doug Chestnut escribió:
Thorsten Scherler wrote:
[...]
The problem with this tmp folders/files are that they are not registered
in lenya and therefore cannot be deleted using the standard delete
method of webdav. This will cause a file not found error.
Further if we do not use
org.apache.lenya.cms.site.usecases.Delete but rather a custom usecase
with some brute force in using IO calls and going directly on the file
system (if document is not registered with lenya) that will fail in the
future with jcr, right?
would these files need to be stored in jcr? couldn't we just store them
in a work/tmp directory. From my understanding, other webDAV editors
try to upload hidden files as well (word). Do we really want to store
this editor specific crap in the repo?
No, that is the point of the comment. ;)
If we assume a work/tmp file directory which is ATM the content/{area}
then we can write a custom delete usecase which will allow the "crappy"
dav client to generate tmp files and clean them again afterwards.
"Crappy" clients behave like:
- create tmp file on dav server
- create *real* file
- remove tmp file
The reason this is needed is that e.g. Dreamweaver assumes that the
destination filesystem contains the same temporary files as the local
filesystem and tries to delete those temporary files when finished.
Doesn't dw also create temp files/dirs to get the server time. This is
the case with ftp anyway.
When we use a custom delete usecase that
1) check whether it is a registered doc
2) if not, try to use IO to remove
then we can support as well "crappy" clients. ;)
We will also need to alter the PUT usecase to recognize the crappy
file/dir name and use IO to write.
wdyt?
Sounds good to me. :)
salu2
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
