[Seaside] Application level state

Philippe Marschall philippe.marschall at gmail.com
Thu Jul 20 11:13:47 UTC 2017

On Wed, Jul 19, 2017 at 6:39 PM, Bernhard Pieber <bernhard at pieber.com> wrote:
> Hi all!
> I have subclassed WASession to add my own session specific state. I would like to do the same for WAApplication. However, I have read in the mailing list that WAApplication is not supposed to be subclassed.
> I tried using preferenceAt:put: to set my root model object. However, I get WAAttribute not found. This feature seems to be for configuration purposes, mostly simple data types and classes.
> So far I used the singleton pattern, a class variable in my root object model class. But now I would like to register the same component class twice using different context paths.
> What is the most idiomatic way to achieve this in Seaside?

Can you go a bit into the details of the state? Is that more
configuration is nature or more a business model?


More information about the seaside mailing list