Not in any really efficient way, far as I know. With a little work, you could probably intercept the upload via groovy, place it on a network drive, replace the attachment with a link to that network file.. But then I'm not sure I can see any real benefit doing it that way. So far my own internal wiki's run at between 5mb and 3gb - with no real noticable difference in performance from the smallest to the largest. Have you taken a look at the documentation for attaching outlook to xwiki? There are some idea's you could work on from doing this - for example, when someone sends an email with an attachment bigger than 20mb, have exchange generate an email to the xwiki system that creates a document with the attachment in it. Remove the attachment from the message, append a link to the wiki document; and you now have an email trail linked to the wiki with no user intervention required. I reckon you could even take the replies, and add them as comments; and any new attachments linked to the comment. [disclaimer: I have never tried using exchange in the above fashion so it may not be doable, but it would be a cool feature for email users to have a web-accessable trail much like Nabble in an internal environment]. -----Original Message----- From: bjquinn [mailto:bjquinn@seidal.com] Sent: 03 August 2007 22:58 To: xwiki-users(a)objectweb.org Subject: [xwiki-users] Xwiki file and attachment storage Hi, we're looking into using Xwiki to replace part of a large Microsoft Exchange setup. The users email large (sometimes 50MB) attachments back and forth to each other and in and out of the company, ballooning the size of the Exchange database, making it too large, corruption-prone, unwieldy, and nearly impossible to back up and/or restore. The fundamental problem with using Exchange for this (beyond the fact that it doesn't provide all the other inherent benefits of a wiki) is that it stores EVERYTHING -- email, attachments, etc., all in one file. We're looking into doing an Xwiki setup to prevent sending these attachments back and forth so much, but my limited ability to audit Xwiki has resulted in me thinking that Xwiki does the same (stores everything in one file/database). Is there any way to store pages in individual files, more like Xwiki's progenitor, Twiki? Or at least for attachments? Thanks! -BJ Quinn -- View this message in context: http://www.nabble.com/Xwiki-file-and-attachment-storage-tf4214945.html#a 11991466 Sent from the XWiki- Users mailing list archive at Nabble.com.

Hi BJ, On Aug 3, 2007, at 11:57 PM, bjquinn wrote: Right now the only storage available is through a relational database. We're working at implementing a JCR storage which will allow you to use whatever supported physical storage you want (files, RDBMS, OODB, etc). Artem had a first implementation done a while ago but I don't think it was ever finished. Artem, would you mind giving us a status on the JCR work and the plan ahead? BTW there's a good reason XWiki uses a DB instead of the file system. File system doesn't allow the type of advanced queries that are required for XWiki. FS are good for storing large number of documents but they're bad for doing queries on them. For attachments, I agree we could use an FS storage. Actually XWiki's architecture already separates the storage for documents from the storage for attachments. It just happens that currently attachments are also stored in the DB. All that said, DB should get you a long way but you'll need to set up indexes in the your DB. For example: http://www.xwiki.org/xwiki/bin/ view/AdminGuide/Database+Administration Thanks -Vincent