On 2/19/2010 11:20 AM, georgehu wrote:
> On 2/18/2010 4:51 PM, Fernando Correa Neto wrote:
>> Hey there,
>>
>> Using beaker is no biggie.
>> In your .ini you need something like:
>>
>> [filter:beaker]
>> use = egg:Beaker#beaker_session
>> beaker.session.key = yourapp.session
>> beaker.session.secre
On 2/18/2010 4:51 PM, Fernando Correa Neto wrote:
> Hey there,
>
> Using beaker is no biggie.
> In your .ini you need something like:
>
> [filter:beaker]
> use = egg:Beaker#beaker_session
> beaker.session.key = yourapp.session
> beaker.session.secret = supersecret
>
> [pipeline:main]
> pipeline = e
It's also possible to use repoze.session, based on ZODB:
http://docs.repoze.org/bfg/1.2/tutorials/zodbsessions/index.html
- C
On 2/18/10 7:56 PM, Tim Hoffman wrote:
> Hi
>
> Yeah I am using beaker on app engine as well with bfg, real easy to
> setup and it works well.
> I am using memcache on ap
Hi
Yeah I am using beaker on app engine as well with bfg, real easy to
setup and it works well.
I am using memcache on app engine as the store at the moment as I
don't mind if sessions
disappear if not used for a little while, but it would be easy to make
writes to the session persist in the datas
Hey there,
Using beaker is no biggie.
In your .ini you need something like:
[filter:beaker]
use = egg:Beaker#beaker_session
beaker.session.key = yourapp.session
beaker.session.secret = supersecret
[pipeline:main]
pipeline = egg:repoze.zodbconn#closer
egg:repoze.tm2#tm
beake