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

Hi Max!
On Mon, 04 Dec 2000, Max Derkachev wrote:

> I doubt. It is only sufficient if you don't want any other storage besides
> filesystem and shared memory. For me, the database storage is needed.
>
true, I agree on that we should use the already existent container classes
to ease their use in conjunction with session save handlers.

> Well, phplib-4 is only wrappers to standard php4 session (with standard session
> modules). No more no less. I do think that such a module to be a part of the
> "PHPLib for PHP4 (C) " :)). It should handle sessions, when standard storage is
> sufficient. But I think the goal of the phplib is to make some complicated
> tasks simple (always been), and we should provide a good interface for custom
> storage of the session data.
+1 yet again.

> > If the storage is your main concern, then i would like to known why you
> > didn't contact me or anyone else on cvs or dev list to offer your help on
> > the issue.
on that, I set watches on session files, and sow no triggers, so I understand
you worked on something w/o letting others know.

> > We have 3 'ports' now. It shows great stupidity (and lack of
> > management) to re-reinvent the wheel and it makes ASP/JSP programmers laugh.

well, I would say I did my job to avoid this, what did you do?

> > Looks like the stupidity points to me first. 15 minutes after i published my
> > solution, it appeared there was a solution already (Theodor, i feel so
> > stupid, i didnt know....... :-))
:) well, no problem. Don't take it as I wrote that just to "impose" it as the
best solution. I took few hours and wrote it just because there were too many
Qs on the php-general about PHPLib session compatibility with PHP4, and PHP4
is far better than 3 and it's session management should be exploited to it's
powers.

You may note in my cvs commit message and in the patch that I invited
everybody to talk about it, but it got still rapidly.

> Well, I've done the work :). I've got a cvs account at phplib's repository, and
> we should deside how to merge our efforts and not to waste our time in this
> flame. I'm ready to commit my patches, so let's deside on a structure of the
> new session module and integrate all three into one.
> I guess some changes ought to be made in a structure of the module to prevent
> conflicts - the user should specify if he intend to use standard session
> storage (Your and Theo's module) or user module (mine). Maybe it should be
> cpecified in prepend.php, so the necessary module would be included. Maybe we
> should make a basic Session class, and then make extensions to it, covering
> standard php4 storage modules and the user module, which uses custom
> containers.
I love this approach, yap. Design custom classes, from simple session
management, with a backward compatible API (as the one in the repository right
now), and then extend that class to enhance the functionalities.

The start as I see it is settling on a session class API( a Session Interface,
to say so).

-- teodor

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