On Thu 03 Jun 2004, Sven Dowideit svenud@ozemail.com.au wrote:
http://members.iinet.net.au/~spos/twiki/bin/view/Homeorgau/StoreRefactor
is the beginings of the ideas, TWiki oriented of course, but I'm interested in seeing what an intersection of the ideas can bring about
I had to read that a few times before I could make sense of it, so sorry for taking a while to reply.
I don't see why CGI::Wiki couldn't be made to cope with more than one store - after all, it just wants to know that when it asks a store for a node, it will get something consistent. See also the ideas for multiple formatters (languages); multiple stores could work this way too. The way of defining which store a node is in could be defined by the wiki application in a number of ways - keyed on the node name, having a list of "try here first, then here, then here", for example.
I'm reading it as your plan is to hierarchise things a lot more than they are in the general "flat namespace" wiki idea - is this what TWiki "topics" are all about? I do prefer having a flat namespace and letting structure evolve as the wiki is used, but I don't object to building in hierarchy support to CGI::Wiki if people want it. It is not going to be a high priority for me unless someone makes it worth my while though - giving me good reasons to do it or offering to do some of the work.
The resource hierarchy idea might be a good way to allow using more than one formatter (language) on a given page.
Finally for search I suggest you take a look at Plucene, a Perl port of Lucene.
Have I missed anything?
Kake