You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Joe Orton <jo...@redhat.com> on 2004/09/13 18:13:45 UTC
Re: cvs commit: httpd-2.0 STATUS
On Mon, Sep 13, 2004 at 03:56:19PM -0000, jerenkrantz@apache.org wrote:
> --- STATUS 13 Sep 2004 15:39:57 -0000 1.751.2.1044
> +++ STATUS 13 Sep 2004 15:56:19 -0000 1.751.2.1045
> @@ -75,16 +75,17 @@
>
> *) mod_dav_fs: Fix indirect lock record handling on 64-bit platforms.
> http://cvs.apache.org/viewcvs.cgi/httpd-2.0/modules/dav/fs/lock.c?r1=1.31&r2=1.32
> + jerenkrantz asks: Won't this break already existing lock DBs?
> +1: jorton
On platforms with sizeof(int) == sizeof(apr_size_t), the change is a
noop, so no break there.
On other platforms, any indirect lock records which have already been
written to the database by the <=2.0.50 code will be corrupt and
unreadable anyway. If no indirect records have been written it doesn't
matter, and any new records which are written by the new code will be
OK.
Hope that makes sense...
joe
Re: cvs commit: httpd-2.0 STATUS
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
--On Monday, September 13, 2004 5:13 PM +0100 Joe Orton <jo...@redhat.com>
wrote:
> On platforms with sizeof(int) == sizeof(apr_size_t), the change is a
> noop, so no break there.
>
> On other platforms, any indirect lock records which have already been
> written to the database by the <=2.0.50 code will be corrupt and
> unreadable anyway. If no indirect records have been written it doesn't
> matter, and any new records which are written by the new code will be
> OK.
>
> Hope that makes sense...
Yup. Thanks! -- justin