[Seaside] Using a filter to commit changes to Magma

Sebastian Sastre sebastian at flowingconcept.com
Sun Jan 30 17:40:20 UTC 2011

yeah, why not?

I did that so:
1. I can discern dynamically which database the app should work with taking the request in mind (in airflowing I use the subdomain)
2. redirect it defensively if the requested thing is weird (think of a typo in the url or something) and
3. if things are right the filter is working for that database before the app tries to get anything done

a big secondary gain of 3 is that you code focusing on one account/database but the app is scalable to attend N

On Jan 30, 2011, at 3:14 PM, nicolas.oury at gmail.com wrote:

> Thank you so much for your answer.
> For something less sophisticated in term of error handling, would something like:
> MySession>> initialize
> super initialize.
> self addFilter: (MagmaFilter new).
> work?
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20110130/8f80f0b5/attachment.htm

More information about the seaside mailing list