Re: File Server and storage

SmallWiki 1 runs under Swazoo so there may be ways of using Swazoo for the less-wiki like stuff. I have some large installers that I provide links to on the wiki, about 4mb, which I don't want to load as a resource into the wiki. Currently, I am simply using VisualWave to serve those files. A VisualWorks image can handle "bloat" pretty well especially via manipulating the Object memory settings. I don't use the ImageSnapshot storage mechanism though, so by image bloat I really mean memory growth. Instead I implemented a Boss based storage which allows me to recover. I thought about using OmniBase, from what I hear it is pretty good for what it is i.e. a lightweight object database. So from my perspective using GOODS for SmallWiki 2 is a good move. The only issue I fear is that I don't know if the Squeak VM will be able to handle the load of file serving , oodms services etc. I have not tested the performance of the Squeak VM in a while. I don't believe it matches the performance of the VisualWorks VM but perhaps it is adequate enough. BTW, SmallWiki 1 (still available in VW if that matters) with some minor extension i.e. Boss storage mechanism, as far as a straightahead wiki which includes a usable permissions framework, seems to do the job fairly well. -Charles On Fri, 17 Dec 2004 04:30:21 +1100, <alistair(a)alphalink.com.au> wrote: -- Charles A. Monteiro