On Thu, 3 Jan 2002, Yasuo Ohgaki wrote: > > Which is perfectly fine as it is IMO. What is the change here that you > > suggest exactly? > > > - Do not use php_session_register_module() > - Add #ifdef to ps_modules struct for external save > handler modules
You want to add the pgsql module here too then? > > Just a few lines of changes, but it requries to compile save handler > modules with session module. > I'm against removing the php_session_register_module() call, for the reason that I need it for SRM. Sascha implemented it because if this (maybe partly) reason. If this call is removed, or deprecated, there is no way for an extension to register a session module, without modifying the PHP Source, which is a bad idea IMO. > > You still failed to tell me why this is all needed. If it's only the > > runtime undefined symbol stuff, then I think it's nto worth the hassle to > > 'fix' it. It's not broken now. And I think it's not that big a problem at > > all. > > That's why I just get rid of error message for now. > > Should I leave it as is? That's my opinion here. > For undefined symbol stuff, you can see with Apache SAPI with session > module, and CGI SAPI *without* session module. Make sure you load > msession or pgsql save handler module in php.ini. Then you will see > "undefined symbol" error in apache error log :) Yeah, I understand this, but having both a Apache SAPI with sessions and a CGI SAPI _without_ sessions wouldn't be that common of a setup. > Both of us know well that users will keep submitting bugs for these > error messages. I would if I don't know internals of PHP :) :) regards, Derick -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
