Re: Session management module - thoughts

This would be perfect! -J Sascha Schumann wrote: > Yes, these user provided functions could be one solution to the problem. If > that does not satisfy the end-user he might choose to create his own ps_module > (stands for PHP session module or persistent save module, whatever you like > better): > > typedef struct ps_module_struct { > char *name; > int (*open)(PS_OPEN_ARGS); > int (*close)(PS_CLOSE_ARGS); > int (*read)(PS_READ_ARGS); > int (*write)(PS_WRITE_ARGS); > int (*delete)(PS_DELETE_ARGS); > int (*gc)(PS_GC_ARGS); > } ps_module; > > I believe this small "API" to be enough for even complexer modules such as the > RPC client/server model which was presented on this list not long ago. We > provide a file based module by default which uses a simple directory to store > its session data. > > The session module is fully configurable. The new generalized INI support made > it possible to implement the configuration part in about a dozen lines. This > part will be extended to provide IPPs with the necessary options to prevent > users from doing malicious things. > > I'm currently working on the serialization part which still has some problems > with correct reference counting and destruction of zvals. > > -- > > Regards, > > Sascha Schumann > Consultant > > -- > PHP Development Mailing List http://www.php.net/ > To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net > For help: php-dev-help@lists.php.net -- ---------------------------------------- | http://motosite.com | | Your motorcycle resource on the web! | ---------------------------------------- | Juan A. Pons | | jpons@motosite.com | | '98 VFR800 - '88 NT650 (Hawk) | | AMA 368441 - HRCA | ----------------------------------------