11 Nov
2010
11 Nov
'10
7:05 a.m.
On 11 November 2010 13:51, Caleb James DeLisle <calebdelisle(a)lavabit.com>wrote;wrote:
The first thing I should tell you is with the windows
installer, all of the
wiki is kept in ram so
you adding large attachments will soon put you in a position of being
unable to load the wiki and
exporting (to move to a .war with a "real" database) will become very
difficult.
So you are saying, if I can't run the wiki, I won't be able to export it and
thus can't move the server to a new platform?
I assume, that once its running in a "real" database, I will not need to
"export" it, but instead I can just use the normal database
backup/restore.... right?
That said, the page you want is
http://yourwi.ki/xwiki/bin/edit/XWiki/XWikiPreferences?editor=object
Expand the section called "XWikiPreferences 1" and you should find the
setting you are looking for.
ok got it, seems to be 33mb limit.
In a postgres database with 1024MB of ram, you will
still find a limit
around 50MB, something we are
working to change.
ouch, how can that be? thats nothing, I know people who want to upload
multi-gigabyte files (rather than posting them on a DVD via snail mail).
I wrote a little C++ cgi app with libcurl, and that uses a streaming
technique so the data is streamed out to the http client, so it doesn't
require any more ram than to load the index of files.
Can't you do something similar in Java? Don't load the file off the
harddisk, instead stream it from the harddisk/database.