Dear Bettual,
Making sure all clients can read them isn't a purpose by itself. I hope you
don't have too many files with 10MB properties, or that you have huge
amounts of memory in your clients: they are designed for small amounts of
data and may be read fully into memory for many files at the same time.
Hope that explains Hyrum's question.
Bye,
Erik.
On Tue, May 25, 2010 at 10:47 AM, Bettual Richter <
Bettual.Richter_extern_at_ppi.de> wrote:
>
>
> Von:
> Ryan Schmidt <subversion-2010b_at_ryandesign.com>
> An:
> Bettual Richter <Bettual.Richter_extern_at_ppi.de>
> Kopie: users_at_subversion.apache.org Datum: 21.05.2010 16:36 Betreff: Re:
> Maxsize of Properties
> ------------------------------
>
>
>
> On May 21, 2010, at 06:39, Bettual Richter wrote:
>
> >>> Ryan Schmidt wrote:
> >>
> >>> On May 20, 2010, at 05:40, Bettual Richter wrote:
> >>>
> >>>> does anyone know if there is some kind of maxsize for revision
> properties ?
> >>>
> >>> I'm not sure.
> >>>
> >>>> I'd like to set long revision properties on a repository.
> >>>
> >>> How large?
> >>
> >> I'm not really sure how large the properties are finally going to be
> >> but lets say like 10 000 000 charaters would be quite desirable.
>
> >Based on the error message "413 Request Entity Too Large", I'm guessing
> that's too large.
>
> >When you're serving your repository via Apache, Subversion properties are
> implemented as WebDAV properties, I think. I found a reference [1] that says
> the WebDAV spec doesn't limit the size >of properties, but that some
> implementations might. I guess maybe Apache and/or Subversion do impose a
> limit of some kind.
>
> >Properties are designed for short strings, like the name of the author,
> the date and time, the log message. It therefore wouldn't surprise me to
> find out that this infrastructure is not >prepared to accept a property with
> 10MB of data.
>
> >If I'm right about Subversion properties being implemented as WebDAV
> properties, then you might have success bypassing WebDAV, i.e. using
> svnserve. Or that might fail too. I haven't tried.
>
>
> >[1]
> >http://books.google.com/books?id=LN6PRtgiwNgC&pg=PA164&lpg=PA164&dq=maximum+size+of+webdav+property&source=bl&ots=RzC0RsrP0A&sig=FeEp0d-X62pSLfvpfQf3He2yX3k&hl=en&ei=9nL2S6KFBIOUMdCPkIQI&sa=X&oi=book_result&ct=result&resnum=10&ved=0CDkQ6AEwCQ<http://books.google.com/books?id=LN6PRtgiwNgC&pg=PA164&lpg=PA164&dq=maximum+size+of+webdav+property&source=bl&ots=RzC0RsrP0A&sig=FeEp0d-X62pSLfvpfQf3He2yX3k&hl=en&ei=9nL2S6KFBIOUMdCPkIQI&sa=X&oi=book_result&ct=result&resnum=10&ved=0CDkQ6AEwCQ>
>
>
> Thanks, at the moment my hint is also the Apache which limits the bodysize
> of a http request.
> Hopefully that's a way to solve this issue but I still have to test it
> first.
>
> We wish to use the Information in properties to make sure every client used
>
> on our repositories is able to read them.
>
>
>
Received on 2010-05-25 16:47:44 CEST