Hi!

Slide already takes care of almost all your meta data:

>  - manage file version
This is done by the deltav versioning extension to webdav, see 
http://www.webdav.org/deltav/protocol/rfc3253.html

>  - show submitter information, file type, file size info
This information is contained in <DAV:owner/>, <DAV:getcontenttype/>, 
<DAV:getcontentlength/>

>  - show locked by
If a resource (document) is locked, it will have a <DAV:lockdiscovery/> 
property. In that property, there is some xml which also mentions the owner of 
the lock. Be aware that reading a locked resource is always possible, however 
writing to it (or affecting is state in any other way) is only possible when 
you specify the lock token, which is also mentioned in the lockdiscovery 
property. So someone can hijack your lock. It is really up to your application 
to get this right, but generally it is not a problem.
See http://www.webdav.org/specs/rfc2518.html#METHOD_LOCK and 
http://www.webdav.org/specs/rfc2518.html#locking for more information.

>  - support folder structure
Webdav organizes documents into folders, called "collections" in webdav terms. 
So does slide, of course.

As I mentioned before, the PROPPATCH method can be used to set arbitrary 
properties, custom ones as well. See 
http://www.webdav.org/specs/rfc2518.html#METHOD_PROPPATCH for more information.

Bye and good luck!
max

> -----Original Message-----
> From: Lixin Chu [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, March 07, 2006 10:55
> To: Slide User
> Subject: common practice of managing metadata with Slide
> 
> 
> Hello,
> would like to seek advice on the common practice of managing 
> metadata with
> Slide.
> 
> i am working on a typical (hopefully) doc management 
> appliaction, which
> requires:
>  - manage file version
>  - show submitter information, file type, file size info
>  - show locked by
>  - support folder structure
> 
> so what's the common way of managing these meta-data info ? 
> should I leave
> them to Slide or should I create a database table to manager these
> information ?
> 
> and which solution gives better performance ?
> 
> thanks in advance!
> lixin
> 

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

Reply via email to