My understanding is that work on WikiWorks has stopped and that SmallWiki is the future.

- Is it possible to configure the simple file server (as described at http://wiki.openskills.net/OpenSkills/Smalltalk+HTTP+Server) to be able to do directory listings if there isn't an index.html in the requested directory (like the WikiWorks FileServerWiki and Apache)?

- Is it possible to store page definitions (with history) outside the image (to prevent image bloat and allow page history to be on disk rather than in memory)?

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

Alistair: Serving files is quite easy from VisualWave. Do the following: Go Parcel Manager>>>Application Server >>> Sugesttions and load: VisualWave VisualWave Demos Click Web Server Console now found on Launcher. Click "Create Server" Choose "Server Type" to be: WaveHttpRequestBroker Change the "hostname" if you like, note that in the case of file serving it is irrelevant i.e. i.e. non-html files , pdf,etc Change the port if you like Click "Create" found at bottom of screen. Click on list entry above for newly created server. Click "Edit Resolver" Click "Add Path" Choose "Resolver Type" to be: VisualWave.FileResponder Enter Path for example "files" Note: path means a token on url used to locate the service, has nothing to do with a path on the file system , sorry had to be said just in case. Click "Accept" Select newly created responder from list on left side pane. Click "Configure Resolver" Change "Default Directory" if you do not like the specified location Click "Accept changes" Click "Back to Resolver" Click "Start" immediately underneath server listings which will activate your server. Then place content under the file system directory associated to FileResponder created above. then go to a web browser preferably Opera and enter something like: http://mydomain.com:9999/files/myfile.pdf, voila. Note that recently, they have re-configured Wave to exist under the Opentalk framework but did not have the time to update the UI's so there are some bugs related to that which you will not encounter if you follow the steps outlined above. For example if you decide you want to "edit" the port number you will encounter a bug associated to an AspectAdaptor assuming it was still adapting the same type of entity. Maybe that is fixed in 7.3. Hope that helps :) -Charles On Wed, 22 Dec 2004 22:05:51 +1100, Alistair Grant <alistair(a)alphalink.com.au> wrote: