[Catalyst] RCF for a Catalyst Wiki Controller

[John Napiorkowski]

There are quite a few models out there to help me
design a storage 'plugin' system where you can easily
swap backend drivers.  Since I'm being paid for this
the first one has to be in Postgres, although I forsee
very little effort in make a SQLite version of it,
based all the examples I've found on CPAN already.

I'm not finding any Kwid text parsers that seem ready
for prime time, but again I will try to separate out
the parser into a plugin so that later on we can drop
in other parsers.

One thing that I am seriously considering is 'dual
parsering' the wiki content through a wiki layout
parser and through Template Toolkit.  This opens a
world of possibilities (and potential security issues)
for the wiki consumers.  Does anyone have any thoughts
on that?

Another thing that will go into this design is some
hooks to the authentication model, since one of my
design requirements is to track who made what change
and when.  I'll make this an optional feature for
people not using authentication/authorization control,
but I will probably have to design this to use the
access control modules based on DBIx for my first
version of this, since that is the model I've chosen
for the website I am creating.  Any thoughts on the
most compatible way to achieve that is also
appreciated.

--john



--- Matt S Trout <dbix-class at trout.me.uk> wrote:

> Kieren Diment wrote:
> > Wiki markup:  Kwid - it's like pod but easier to
> write.  Should parse to 
> > the same kind of tree. It's also not quite fully
> implememted yet, so 
> > there's the possibility to influence the
> development of the final standard.
> > 
> > It would be useful also to be able to use
> different stores other than 
> > RDBMS easily.  The filesystem is good quick and
> dirty modelling of 
> > heirachical information (e.g. biological
> classification schemes is a 
> > classic heirachical info store), so making the orm
> optional or taking 
> > some steps to make it easily swapped with a
> different model out would be 
> > good in my opinion.
> Absolutely agreed, I'm currently experimenting with
> a double-layer MVC 
> approach where I have one MVC for the domain model
> and the app itself is 
> a second MVC whose model merely interacts with
> domain view and 
> controller objects (for those of you following along
> the "stealing from 
> Jifty" part, this is not unlike the Jifty action
> approach although Jesse 
> and I can probably claim "parallel invention" rights
> given we've been 
> discussing this sort of stuff for close to a year
> now).
> 
> The nice thing about this approach is that provided
> you present the 
> appropriate domain view/controller interfaces you
> can swap out the 
> underlying implementation trivially since your
> DBIx::Class or similar 
> objects never leak outside to the UI/web layer.
> 
> _______________________________________________
> Catalyst mailing list
> Catalyst at lists.rawmode.org
> http://lists.rawmode.org/mailman/listinfo/catalyst
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com