Re: [phplib-dev] Fw discussion 4: [phplib] PHPlib session using PHP4 sessions implementation: the code From: Teodor Cimpoesu (teo <email protected>)
Date: 11/30/00

Hi R.B.!
On Thu, 30 Nov 2000, R.B. Scholtus wrote:

> > > "This goal of this extension of phplib is to let phplib use PHP4 native
> > > sessions instead of using a database for storing sessions data."
> > I should have written '... instead of using phplib's default storage, a
> > database.' I hope that it is clear to you and everyone else that with the

I would reform and say it straight that PHPLib session API is to be rewritten
to use PHP native session API (which futher suports this and that) and to
enhace the current one with backward portability in mind.

> > A little bit off-topic, but still important:
> > For high traffic sites, probably the fastest way of doing sessions is to
> > store the session data in memory. This should be as easy as storing the
> > files on a ramdisk (is that called virtual disk?) instead of in /tmp and
> > adding some RAM maybe. But this is just a wild guess, im not a expert on
> > this kind of administration!!! Anyone here who is? Please help us, i know
> > some people who want to know!!!
session.save_hander = mm

> box
> > is different........
> > The, for example, serialize() function is this there while not being used
> by
> > the phplib-4 extension. Just in case someone uses it! (why???)
I wrote a preliminary session4.inc and marked some of the useless functions
as obsolete and invited everyone to vote on pruning them.

I am still willing to see a really clean API ...

> > native sessions or not. But this decision is just a config thing, it
> doesn't
> > affect our actual code, so the hell with it :-)))
I wouldn't go with such "click-me-wizard" thing. The webmaster should know
what's install and what wants to run, IMO.

my .2 euro

-- teodor

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-dev-unsubscribe <email protected>
For additional commands, e-mail: phplib-dev-help <email protected>