The ideal here, of course, would be for versioning to store deltas. If a
property changes, record the change in the property alone, etc. If the
content is text and the content changes, store a diff, not a new copy (much
like CVS). If the content is binary, then store a binary delta. There
Hello,
I'm wondering if someone could tell me how to have multiple WebdavResource
instances participate in a single transaction?
Thanks,
Andy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
I'm using WebdavResource to access a Slide WebDAV servlet. My question is
simple: do I need to call lockMethod when using transactions? For example,
do I have to do something like this:
resource.startTransaction(...)
resource.lockMethod(...)
or
resource.lockMethod(...)
I submitted code a few weeks ago to accomplish something very similar. You
will still have to write a few simple methods (by implementing a DAO style
interface) to retrieve your users from MySQL, but my contribution takes care
of mapping your user info to the principal store format that Slide
WebDAV is only part of our architecture. We have rich clients that also
communicate with services via Spring's http based remote protocol and via
JMS. Sometimes the client may access a document directly, but sometimes the
client may invoke a service which then needs access to a document. The
OK, I've coded my own Principal store based on code from JNDIPrincipalStore
and am setting up a test configuration. I'm a little confused how to setup
domain.xml. First, my store will only handle /users and /roles. Everything
else will be handled by J2EEStore. So, do I setup two separate
are appreciated. :)
- Andy
On Tuesday 08 February 2005 07:00 pm, Carlos Villegas wrote:
Andy Depue wrote:
None of these options seem very palatable to me. Am I missing something?
Does Slide really not provide an easy way for me to supply it with the
currently authenticated user AND his/her
OK, I need ACLs and versioning so I guess WCK isn't for me. The one thing I
want to avoid in my system is duplicating security information for a user.
This would be the username, password, and the user's roles. We already
manage user/passwords/roles in our system, and would like Slide to use
I'm wondering if anyone would mind sharing their experience with the WebDAV
Construction Kit? How stable have you found it to be? Also, can I support
ACLs and versioning with the kit? I know the site says you can't, but I'm
hoping that has changed. :)
- Andy
product. I don't do ACLs
or versioning. Our QA folks recently put 250 million files via 20
threads through slide into our archive without any errors. The narrow
paths that we have exercised seem stable to me.
-John
Andy Depue wrote:
I'm wondering if anyone would mind sharing their experience
10 matches
Mail list logo