[Cosmo-dev] content sizing

Brian Moseley bcm at osafoundation.org
Tue Oct 3 11:32:06 PDT 2006


bug 6761 (<https://bugzilla.osafoundation.org/show_bug.cgi?id=6761>)
requires that we establish limits on the size of item content and item
attribute values these values map to the maximum size of a dav
resource that can be PUT and the maximum size of of a dav property
value that can be PROPPATCHed.

our current database sizing allows item content to be up to 100mb and
attribute values to be up to 1kb. what do you folks think about these
values? too large? too small?

re item content - 100mb just intuitively seems too big. when i think
about sharing with cosmo, i don't think of things that large. most
documents in a collaborative environment won't be anywhere near that
big. even photos aren't that big. the only things i can think of in
that neighborhood are software packages (videos too, but those may
well be a lot larger). i guess i could imagine people using cosmo as
an rpm server, but maybe those people would be okay with recompiling
cosmo with larger sizing?

re attribute values - i'm a little concerned that clients might want
to set dav properties containing big xml documents, so 1k feels a
little small. that said, i haven't seen in the real world anything dav
property values that don't fit into 1k.

i'm leaning towards going with 10mb and 1kb and recommending that
people who need more manage their own build of cosmo. of course we can
change these limits in the "true" build if real world experience shows
that people really do need more.

thoughts?


More information about the cosmo-dev mailing list