session keeping?<br>maybe config with ip_hash can help you to do this job.<br>and the document <a href="http://wiki.codemongers.com/NginxHttpUpstreamModule">http://wiki.codemongers.com/NginxHttpUpstreamModule<br></a><br><div class="gmail_quote">
On Wed, Oct 22, 2008 at 7:08 PM, Dave Cheney <span dir="ltr"><<a href="mailto:dave@cheney.net">dave@cheney.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
eh, depending on what you're storing couldn't it hit the RFC cookie<br>
limit pretty easily?<br>
</blockquote>
<br></div>
The only piece of data you would need is the user id. Everything else can be deduced from that.<div class="Ih2E3d"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
i suppose it has some sort of key and expiry in it so people can't<br>
spoof alternate expiry times etc.<br>
</blockquote>
<br></div>
Not really sure, haven't used it in production and I'm not working with rails at the moment. You make a good point thou, you probably need two things, the user id, and an expiry time encoded in the cookies value.<br>
<br>
Cheers<br><font color="#888888">
<br>
Dave<br>
<br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>The time you enjoy wasting is not wasted time!<br>