Il giorno gio, 01/03/2007 alle 09.27 +0100, Tiziano Faion ha scritto:
in the afternoon i'm working on it.I'll let you know how i solve the
problem.
I've solved, it was easier than what i thought.
In Yaml of both apps i added
cookie_path: '/'
cookie_name: 'something_session'
under
Il giorno mer, 28/02/2007 alle 14.14 +, Ian Docherty ha scritto:
I might be asking the blindingly obvious, but do the two applications
use the same domain?
Yep sure;)
in the afternoon i'm working on it.I'll let you know how i solve the
problem.
Thanks for suggestions
--
Tiziano [EMAIL
Hi All,
I've got a trouble in sharing data session betweeb two catalyst
applications.
The First one is an intranet software where user log in.
The second one is a production monitoring software.
In intranet i've a link that opens, in the same window, the second app.
Two apps shares same database
we have just improved our session implementation. instead of storing
our session table in mysql database, we stored them in memcache. we
got immense speed improvement from the change. memcache is completely
separate from catalyst, may be it will work for you too.
On 2/28/07, Tiziano Faion [EMAIL
I might be asking the blindingly obvious, but do the two applications
use the same domain?
If not sessions will not work between them because the session ID is
normally stored in a cookie which cannot be passed between domains.
You may have to pass the cookie in the URL in that case.
On 2/28/07, Jeffrey Ng [EMAIL PROTECTED] wrote:
we have just improved our session implementation. instead of storing
our session table in mysql database, we stored them in memcache.
Memcached does things like silently drop your data when it runs out of
room. If the daemon stops for any
right! thanks for reminding. we probably will put it on a separate
dedicated memcache server then.
On 2/28/07, Perrin Harkins [EMAIL PROTECTED] wrote:
On 2/28/07, Jeffrey Ng [EMAIL PROTECTED] wrote:
we have just improved our session implementation. instead of storing
our session table in
On 2/28/07, Jeffrey Ng [EMAIL PROTECTED] wrote:
right! thanks for reminding. we probably will put it on a separate
dedicated memcache server then.
That won't help. If you want reliable session storage with caching,
use memcached as a write-through cache for your database, i.e. when
you write,
