vmassol wrote:
However I'm curious to know why you need attachments stored in the
file system.
Because many of these attachments may be large (50MB), and over time the
database can grow to be unweildy. Currently that's our problem with our
exchange server setup (people keep emailing
Vincent Massol wrote:
Definitely. For this use case, webdav support would probably be the
best. We have jira issues opened for this but nobody has implemented
it yet AFAIK. I guess if the JCR implementation also supports Webdav
that should work too.
-Vincent
Is that what you mean? And is this Jackrabbit
stuff ready by v1.1?
Nope. This is 1.2 stuff.
Well, 1.2 is almost here... is the jackrabbit stuff ready, and can I store
attachments in files??
--
View this message in context:
Hi,
On Oct 30, 2007, at 9:03 PM, bjquinn wrote:
Is that what you mean? And is this Jackrabbit
stuff ready by v1.1?
Nope. This is 1.2 stuff.
Well, 1.2 is almost here... is the jackrabbit stuff ready, and can I
store
attachments in files??
Sorry but no. The scope for 1.2 was changed
Vincent Massol wrote:
Sorry but no. The scope for 1.2 was changed a long time ago. More
importantly Artem who was working on it has stopped participating to
XWiki for some time since he's busy on other stuff. He'll join us back
later but there's no ETA right now on the JCR
http://jackrabbit.apache.org/faq.html#whats-fs wrote:
What is a Jackrabbit file system?
A Jackrabbbit file system (FS) is an internal component that
implements standard file system operations on top of some underlying
storage mechanism (a normal file system, a database, a webdav
On Aug 30, 2007, at 5:19 PM, bjquinn wrote:
http://jackrabbit.apache.org/faq.html#whats-fs wrote:
What is a Jackrabbit file system?
A Jackrabbbit file system (FS) is an internal component that
implements standard file system operations on top of some underlying
storage mechanism (a
