On Sun, 29 Jun 2008, Perrin Harkins wrote:
On Sat, Jun 28, 2008 at 9:48 AM, Jeff Peng [EMAIL PROTECTED] wrote:
But I have a question, does nginx support for session-keeping?
A user's request, should go always to the same original backend server.
Otherwise the user's session will get lost.
On Mon, Jun 30, 2008 at 3:18 AM, James Smith [EMAIL PROTECTED] wrote:
I would consider using a shared memory solution to save traffic too
from the database server (consider a solution based on memcached??)...
No, don't use memcached for sessions. It's a cache, not a database.
It trades
Thanks for all.
what's the standard module for storing sessions in a database?
On Mon, Jun 30, 2008 at 8:43 PM, Perrin Harkins [EMAIL PROTECTED] wrote:
On Mon, Jun 30, 2008 at 3:18 AM, James Smith [EMAIL PROTECTED] wrote:
I would consider using a shared memory solution to save traffic too
from
On Mon, Jun 30, 2008 at 11:00 AM, Jeff Peng [EMAIL PROTECTED] wrote:
what's the standard module for storing sessions in a database?
I recommend CGI::Session.
- Perrin
On Mon, Jun 30, 2008 at 11:07 PM, Perrin Harkins [EMAIL PROTECTED] wrote:
On Mon, Jun 30, 2008 at 11:00 AM, Jeff Peng [EMAIL PROTECTED] wrote:
what's the standard module for storing sessions in a database?
I recommend CGI::Session.
Yes, currently I'm also using CGI::Session.
How about
On Mon, Jun 30, 2008 at 11:09 AM, Jeff Peng [EMAIL PROTECTED] wrote:
How about Apache::Session? Is it more efficient under modperl?
No, it's about the same, and CGI::Session is better maintained. Don't
be fooled by the name: CGI::Session works well with mod_perl.
- Perrin
nginx as a light http\smtp server. It does not do any specific request
logic - it specially designed to minimize request cycle times.
On Sun, Jun 29, 2008 at 5:03 AM, [EMAIL PROTECTED] wrote:
You can specify 'stickysession' which is the name of the cookie or
request param used for session.
On Sat, Jun 28, 2008 at 9:48 AM, Jeff Peng [EMAIL PROTECTED] wrote:
But I have a question, does nginx support for session-keeping?
A user's request, should go always to the same original backend server.
Otherwise the user's session will get lost.
I would advise you not to do this. It's a
Hello,
We have some modperl application servers.
Follow the suggestion on this list, I will use a nginx in front of
them to do the load balance.
But I have a question, does nginx support for session-keeping?
A user's request, should go always to the same original backend server.
Otherwise the
http://wiki.codemongers.com/NginxHttpUpstreamModule
IP hash based distribution is probably what you want
On 6/28/08, Jeff Peng [EMAIL PROTECTED] wrote:
Hello,
We have some modperl application servers.
Follow the suggestion on this list, I will use a nginx in front of
them to do the load
On Sat, Jun 28, 2008 at 10:14 PM, [EMAIL PROTECTED] wrote:
http://wiki.codemongers.com/NginxHttpUpstreamModule
IP hash based distribution is probably what you want
Thanks.Source IP hash sounds a possible way.
But, if user's gateway (for local network) has a IP pool, it means the
first time
If you're looking for cookie based session affinity, i suggest you
also look at apache+mod_proxy.
You can specify 'stickysession' which is the name of the cookie or
request param used for session.
Cheers,
Bharanee
12 matches
Mail list logo