Camping and sessions proposal.

[Aria Stewart]

On Oct 9, 2007, at 6:52 PM, Julian 'Julik' Tarkhanov wrote:

>
> On 10-okt-2007, at 0:09, Jonas Pfenniger wrote:
>> ActiveRecord doesn't seem to handle
>> hashid as an identifier, plus it doesn't seem to be fully consistent
>> across the various RDBMS.
> Only if you want to totally insist and not give it an ID then yes, it
> becomes a kind of a nuisance (your insistance is not
> justified though, as I mentioned in the ticket) because an integer is
> actually quite big.
> You gain little on the cleanness side, but you lose on the
> implementation and compatibility.

Yeah, AR demands an ID for most cases, and complains bitterly without.

>
>> On the other hand, the scope of the project
>> does not permit to implement all kind of client persistence.
> +1

++

>
>> So here is what I propose : Camping will only provide an in-process
>> session store with no real security built-in. See it as a hack-ready
>> example that will allow you to make your internal apps work quickly
>> (ak. no DB dependency).
> -1
> If we sooo want to dump the DB, why not use PStore? I think
> multiprocess sessions are a must. Be aware that the RAM is not
> rubberized either.
> I like the implementation with load_state / save_state but I wonder:
> a) in-mem sessions are nasty, please don't
> b) how is that supposed to work with many applications on one server?
> which application decides which session driver is going to be used?
>
> If you ask me, I'd say sessions should stay with the DB (also
> considering that people are using them and there are session records
> in the wild).
> Give AR that ID and let it shut up :-)
>

Agreed -- though I actually need both in-memory sessions and on-disk.  
I'm using Net::IMAP, with persistent connections, and those are  
obviously not marshallable. Making it easy to create either based on  
the hooks camping provides is the best way I can think of.

I'd love to have camping not actually create sessions on its own, but  
provide a session lib that works when required, like camping/ 
session.rb does now (ish); I'd love to have a version that doesn't  
require active_record, but most of my apps do at least use an sqlite  
database anyway.

Keep camping light, move sessions as far out of the core as possible!

Aria