Hi Lou,
If they're common across every instance of your application you could
also just put them on the class-side of an appropriate class in your
project (perhaps even your session subclass).
But, yes, if you have data that is common across all sessions of a
single instance of an application (but you want to allow multiple
instances of the application in the image at one time with different
data) you can certainly subclass Application. To use your subclass, go
to /seaside/config (or wherever you have the config app installed) in
your browser and under "Add Entry Point" choose the class and give it
a name.
You could also consider creating your own Configuration class if the
per-application data is just configuration state.
Julian
On Thu, Jan 29, 2009 at 5:22 PM, Louis LaBrunda
<
[hidden email]> wrote:
>>Hi,
>
>>I have some methods and data that are common across Seaside session...
>
> I'm sorry. My first sentence may be a little unclear. The methods and
> data that I am talking about are the same across all sessions. Therefor,
> these methods and data don't need to be repeated in each session. A single
> copy living in a subclass WAApplication will be fine. Hence the rest of my
> question.
>
>>For now I have a subclass of WASession and put the methods and data in there.
>>Should I subclass WAApplication and put the methods and data there? And if
>>I should subclass WAApplication, how do I get my subclass to be used
>>instead of WAApplication? Thanks in advance for all opinions.
>
> Lou
> -----------------------------------------------------------
> Louis LaBrunda
> Keystone Software Corp.
> SkypeMe callto://PhotonDemon
> mailto:
[hidden email] http://www.Keystone-Software.com>
> _______________________________________________
> seaside mailing list
>
[hidden email]
>
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside>
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Locked
