You are viewing a plain text version of this content. The canonical link for it is here.
Posted to zeta-dev@incubator.apache.org by Guillaume Kulakowski <gu...@llaumgui.com> on 2010/06/23 05:46:51 UTC

[zeta-dev] WebDAV and MySQL lock

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

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.

Thx.
- -- 
Jabber/Gtalk : llaumgui@gmail.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkwhn8sACgkQGL+mH11RLJdvGQCeNRTegFrMmRRWrLj9oj88mSHc
nx4An0xOr1/qVUs8UUlFtq0zlYnkD/qb
=gggr
-----END PGP SIGNATURE-----

Re: [zeta-dev] WebDAV and MySQL lock

Posted by Tobias Schlitt <to...@schlitt.info>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On 06/23/2010 09:42 AM, llaumgui wrote:

> 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.

these are 2 different things. In MySQL you handle WebDAV lock, i.e. if a
user issues a "LOCK this directory" command, this is stored in the DB.
What still exists on you file system are locks to avoid concurring
access by paralell HTTP requests. The .ezc/ directories e.g. store the
WebDAV properties of your files (e.g. MIME type), which has nothing to
do with locking.

To get rid of these, you'd need to overwrite property handling in the
back end or implement a custom back end. Have a look at
ezcWebdavSimpleBackend and friends for this.

HTH,
Toby
- -- 
Tobias Schlitt         tobias@schlitt.info       GPG Key: 0xC462BC14
a passion for php                     http://schlitt.info/opensource
eZ Components are Zeta Components now!          http://bit.ly/9S7zbn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwhvsUACgkQ5bO3TcRivBQKBgCgmbnJc3UX2Ni/29kTh83Q7W6W
XRYAoLsuOFw0WrmIjGywJ8YNBhzj42Kr
=033E
-----END PGP SIGNATURE-----

Re: [zeta-dev] WebDAV and MySQL lock

Posted by llaumgui <gu...@llaumgui.com>.
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 <to...@schlitt.info>:
> -----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

Re: [zeta-dev] WebDAV and MySQL lock

Posted by Tobias Schlitt <to...@schlitt.info>.
-----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
- -- 
Tobias Schlitt         tobias@schlitt.info       GPG Key: 0xC462BC14
a passion for php                     http://schlitt.info/opensource
eZ Components are Zeta Components now!          http://bit.ly/9S7zbn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwhs+oACgkQ5bO3TcRivBQfswCgksBB6WtpDUBJWD8nCD6khFIU
H7EAn1wmh/ytCPMM0+e2fKQpe+2pPI2Y
=hHYb
-----END PGP SIGNATURE-----