> create table asp_state (
> group_id varchar(12) NOT NULL,
> state_id varchar(32) NOT NULL,
> subkey varchar(200) NOT NULL,
> deletion datetime NULL,
> data text/long,
> primary key(group_id, state_id, subkey)
> )
what is group_id ? (sorry haven't dug current sessions implementation yet,
I'll get to it ASAP )
varchar indexing is rather slow under many SQL servers/version, maybe
there could be something faster?
(as I understend there would be a lot of search on group_id, state_id and
subkey )
> However $Session will be default likely behave like
> an Apache::Session, with all the data being read
> at the beginning of the request, and written out
is this really neccesery?
> code complexity. If someone wanted the flat model,
> and it wasn't built into Apache::ASP, then they
> could just use Apache::Session.
What are the advantages of flat model?
I think I don't fully understand it.
> Also, where to get the database connection?
oh. tricky.
I have no idea. Why not adopt what Apache::AuthDBI does?
Although that way there would be no way to re-use that connection.
Hmm, but re-using that connection would mean that apache session would
use applications database and pollute it with it's tables.
I think sessions should be more transparent and less invasive by default.
--
Dariusz Pietrzak
Certified Nobody
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
