From zeta-dev-return-45-apmail-incubator-zeta-dev-archive=incubator.apache.org@incubator.apache.org Wed Jun 23 07:42:52 2010 Return-Path: Delivered-To: apmail-incubator-zeta-dev-archive@minotaur.apache.org Received: (qmail 24721 invoked from network); 23 Jun 2010 07:42:52 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 23 Jun 2010 07:42:52 -0000 Received: (qmail 72356 invoked by uid 500); 23 Jun 2010 07:42:52 -0000 Delivered-To: apmail-incubator-zeta-dev-archive@incubator.apache.org Received: (qmail 72279 invoked by uid 500); 23 Jun 2010 07:42:51 -0000 Mailing-List: contact zeta-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: zeta-dev@incubator.apache.org Delivered-To: mailing list zeta-dev@incubator.apache.org Received: (qmail 72271 invoked by uid 99); 23 Jun 2010 07:42:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Jun 2010 07:42:50 +0000 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=AWL,FREEMAIL_FROM,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of llaumgui@gmail.com designates 74.125.82.175 as permitted sender) Received: from [74.125.82.175] (HELO mail-wy0-f175.google.com) (74.125.82.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Jun 2010 07:42:44 +0000 Received: by wyb40 with SMTP id 40so322549wyb.6 for ; Wed, 23 Jun 2010 00:42:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:sender:reply-to:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:content-type; bh=AOD/7QU1vXKAtlStlvEbTf+yowX6gvpl1FVXLsecbcY=; b=ExRPC67f3Coc/1B18L2N51KusF3owTmJ06zI8z0akQnIlnR+xPEY+q2h4gbyRgoYe5 yVDP8Yx6qiwzQDEyNOzZboSs9mZ9UeJIA5/QP92erdj9BMh3VqpEiI8ZG8mwrdAjonfp 4jKkA1/qv5aWgxe//fkODVChASnhAPni6tXrw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; b=shc6ZNbGVkzry5XS2Q5n1pPmG2HPk+hFJARpu18mv63/VcJmzLquuDGRxazgBhipbO ZmCv+BJzjYlbWX+zBogwsZO8s4wePNXZfgMq/8OPUW4CnTWHBz6r0ORYagc2lxy7n+XI XOPZ3BNLEpo65VM6MR1Pufra+Za47gpfz0Py4= Received: by 10.216.93.81 with SMTP id k59mr5521293wef.92.1277278943657; Wed, 23 Jun 2010 00:42:23 -0700 (PDT) MIME-Version: 1.0 Sender: llaumgui@gmail.com Reply-To: guillaume@llaumgui.com Received: by 10.216.50.67 with HTTP; Wed, 23 Jun 2010 00:42:03 -0700 (PDT) In-Reply-To: <4C21B3EA.1060904@schlitt.info> References: <4C219FCB.4070207@llaumgui.com> <4C21B3EA.1060904@schlitt.info> From: llaumgui Date: Wed, 23 Jun 2010 09:42:03 +0200 X-Google-Sender-Auth: P0aJK4cpFpAwqfFEgls3llAa790 Message-ID: To: zeta-dev@incubator.apache.org Content-Type: text/plain; charset=UTF-8 Subject: Re: [zeta-dev] WebDAV and MySQL lock Hi, the problem is that I have 2 systems : - MySQL lock - file system lock. The custom lock auth add a lock system but don't replace the .ezc/filename.ext.xml system. Thx 2010/6/23 Tobias Schlitt : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Guillaume, > > On 06/23/2010 07:46 AM, Guillaume Kulakowski wrote: > >> is there a solution for use WebDAV lock in MySQL database ? The reason >> is principaly for an historisation of the modification. >> >> I have writing a "myCustomLockAuth" but, MySQL lock is in more of the >> file system lock. > > I don't get the problem you try to describe. Can you elaborate some > more? Storing the lock information using a custom auth class should work > fine, except for it might result in performance issues for big setups. > I'd recommend a memcache variant here. But, what is your exact problem? > > Regards, > Toby -- Jabber/Gtalk : llaumgui@gmail.com