[Seaside] About DB connections pool

[Todd Blanchard]

My strategy is to create a class variable on my session class and  
stick it there if its an application global.

Just one more option for you.

-Todd Blanchard

On May 26, 2006, at 8:19 AM, Maurzio Boriani wrote:

> On 2006-05-26 16:20:11 +0200 Boris Popov <popov at shaw.ca> wrote:
>
>>> may be I found :) I subclassed WAApplication and add it an  
>>> instance var
>>> (dbPoll) with its access method (which return a new dbPool if nil).
>>> This seems to works as expected :)
>> Doesn't mean its limited to Seaside apps though,
>> WAApplication allInstances collect: [:ea | ea dbPool]
>> But like I said, so long as you don't think of it as means of  
>> limiting the access, localizing these types of the things on a per- 
>> application basis sounds fine to me.
>
> obviously on a smalltalk system I don't expect to have something
> 'private', 'isolated' and 'secure' at 100% (at least without the  
> use of some
> capability system). But this (an instance per seaside app) wa
> exactly what I was looking for :)
>
> thanks for your help :)
>
> bye
>
> -- 
> Maurizio Boriani
> GPG key: 0xCC0FBF8F
>  => E429 A37C 5259 763C 9DEE  FC8B 5D61 C796 CC0F BF8F <=
>
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside