Date: 12/04/00
- Next message: lists <email protected>: "[phplib-dev] subscribe lists <email protected>"
- Previous message: Teodor Cimpoesu: "Re: [phplib-dev] Re: [phplib] PHPlib session using PHP4 sessions implementation: the code"
- Next in thread: Teodor Cimpoesu: "Re: [phplib-dev] Re: [phplib] PHPlib session using PHP4 sessions implementation: the code"
- Reply: Teodor Cimpoesu: "Re: [phplib-dev] Re: [phplib] PHPlib session using PHP4 sessions implementation: the code"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Teodor!
Teodor Cimpoesu wrote:
> > 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 problem with it is that the handlers for session_set_save_handler()
ought to be simple functions, not class methods. the function takes only
string arguments, so we have to use wrappers for class methods outside
the class, and session_set_save_handler() should refer to those
wrappers. And, because of this, the task could not be done only by
constructing Session_* inheritance chain.
We need a php function similar to xml_set_object(), say, named
session_set_object( string name_of_sess_object), that could bind session
engine to an object, and, hence, arguments for
session_set_save_handler() would be interpreted as that object's class
methods, similarly to the xml php module.
Maybe Sascha Schumann (I hope he is reading this thread) would help with
this? I'm not a C professional (pitiful).
Till now, the only way to go is to include different files with
corresponding Session stuff for both of the storage modules (standard
ones or user).
> The start as I see it is settling on a session class API( a Session Interface,
> to say so).
>
It has existed before and well documented in the PHPLib docs :). Do we
have to redesign the whole class? It could break the compatibility with
apps that was built using PHPLib and PHP3.
-- Best regards, Max A. Derkachev mailto:kot <email protected> Symbol-Plus Publishing Ltd. phone: +7 (812) 324-5353 http://www.Books.Ru -- All Books of Russia--------------------------------------------------------------------- To unsubscribe, e-mail: phplib-dev-unsubscribe <email protected> For additional commands, e-mail: phplib-dev-help <email protected>
- Next message: lists <email protected>: "[phplib-dev] subscribe lists <email protected>"
- Previous message: Teodor Cimpoesu: "Re: [phplib-dev] Re: [phplib] PHPlib session using PHP4 sessions implementation: the code"
- Next in thread: Teodor Cimpoesu: "Re: [phplib-dev] Re: [phplib] PHPlib session using PHP4 sessions implementation: the code"
- Reply: Teodor Cimpoesu: "Re: [phplib-dev] Re: [phplib] PHPlib session using PHP4 sessions implementation: the code"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

