Session handling busted on Oracle

[Julian 'Julik' Tarkhanov]

On 5-okt-2007, at 17:54, Jonas Pfenniger wrote:

> I think that I have corrected that last week changeset [226]. The
> problem was that Session uses it's own kind of id (hashid) and that by
> default, ActiveRecord uses an incremental version.
>
> See : http://code.whytheluckystiff.net/camping/changeset/226
>
> Please tell me if I introduced any regression.

I am for the proposal of having multiple session drivers, but totally  
_not_ for the proposal of abolishing
the db sessions. I routinely run Camping in parallel fashion  
(multiplexed dispatchers) and I also store
data that does not fit in the 4K cookie limit in the session (see  
Pasaporte, where the whole OpenID request
is piggybacked in the session storage). I also like the idea that all  
Camping apps store their session in _one_ record,
with many apps on one domain this would not be easily solvable  
because 4k is too small for one app, let alone many apps.
So I am for a PStore-based session but not for cookie-based sessions.  
Their introduction in Rails among others revealed some problems that
exist with this approach.

The changeset did not introduce any regressions for me but I will  
keep my Set-Cookie workaround for a while, at least until Camping 1.6  
hits the streets

-- 
Julian 'Julik' Tarkhanov
please send all personal mail to
me at julik.nl