[PWS] PWS only meant for Swiki?

Russell Allen russell.allen at firebirdmedia.com
Tue May 4 00:09:13 UTC 1999


>On Mon, 3 May 1999, Lex Spoon wrote:
>
>>
>> > >I am curious how, in practice, a Swiki performs.  In particular, how
>> > >practical are these things for communities of several hundred people?
>> >
>>
>> The current Swikis haven't been optimized much at all, but as Mark
>> Guzdial posted earlier, they are handling his ~100 student sophomore
>> class without trouble.
>

One solution which I have been using is the excellent CachedSwikiAction,
which writes copies of the rendered HTML files to disk at the time they are
edited, and allows them to be served by Apache.  This enables me to run a
swiki on hardware which otherwise would be a bit on the slow side (some old
Sun IPXs), as well as allowing more than one machine to serve pages in
parallel. ( I still haven't worked out how to get more than one machine to
*edit* swiki pages in parallel :)

>One thing I think would nice is if the text and the "metadata" of a
>Swikipage were stored in separate files. Right now, you only save things
>like name, edit time, etc. when you edit the page. Thus, if your server
>crashes you lose all metadata since the last edit or image save.
>
>On the other hand, I'm eager to see some sort of PWS connection to
>MinneStore. Now *that* will be interesting.
>
>Cheers,
>Bijan

I would have to agree that the current method of storing swiki pages is not
ideal - it makes it hard to do things like merge pages into new swikis,
rename swikis etc. I had been toying with ideas such as storing in XML/HTML
etc, but linking PWS into Minnestore is a wonderful idea! What I would
really like to see a PWS where URLs refer to objects (on or off image)
which know how to serve themselves...

cheers,

Russell


----------------------------------------
Russell Allen

russell.allen at firebirdmedia.com

----------------------------------------





More information about the Squeak-dev mailing list