I needed a session specific time-out (instead of the fixed one in Yaws),
which I thought might be interesting to others (saw some people talk
about it here).
So I added a TTL (Time To Live??) value to the 'new_session' call:
and added the TTL to the internal cookie record. If you do not send
a TTL then the default fixed value kicks in. Attached is the patch
1) Change the session time-out by making a similar change to
2) Make the session time-out configurable in yaws.conf. This would require a
A question for my understanding of replace_session:
Is there a reason why the cookie record is inserted twice in the ets table
After testing it seems like a bug to me as the old time-out remains !
PS and with regards to diff, I sit on a Solaris box and GNU diff is not
so I hope you get it in a correct format.
<<session1.diff>> <<session2.diff>> <<session3.diff>>
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
Get latest updates about Open Source Projects, Conferences and News.