Re: [PHP4BETA] sessions via mm?
| From: | Andrei Zmievski | Date: | Fri, 17 Mar 2000 15:27:09 +0000 |
| Subject: | Re: [PHP4BETA] sessions via mm? | ||
| References: | 1 2 3 4 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-12329@lists.php.net to get a copy of this message | ||
You're correct, something is wrong here. Sascha?
On Sat, 18 Mar 2000, Alan van den Bosch wrote:
> On Sat, 18 Mar 2000, you wrote:
> >On Sat, 18 Mar 2000, Alan van den Bosch wrote:
> >> The module pointers, the phpext_blahblah type entries, are contructed
> >> from the module directory name, not the contents of the module directory. As a
> >> result the phpext_session pointer is included, but the extra session handling
> >> modules pointers are missed (they share the ext/session directory with the
> >> session module). Is this a bug ? It does enforce a policy of one extension per
> >> directory, which the session handling modules break.
> >
> >No, --with-mm is used to enable the mm library support if you have it
> >installed. This library is what's used by the session mm handler.
> >Session module doesn't break anything.
> >
> >-Andrei
> >* All of the above is my opinion, unless specified otherwise. *
>
> Andrei,
> Sorry if I was a little vauge, I didnt intend to imply that there was
> anything "wrong" with the session code, but that there is an anomly with the
> configure process with regards to sessions that do not have there own
> directories.
>
> Looking at ext/session/config.m4 if the option --with-mm is passed to configure
> then the macro PHP_EXTENSION(ps_mm) is executed. To my understanding this
> should enable support of sessions to be stored using mm through a php extension
> module named along the lines of ps_mm.
>
> Take a look at the definition of the PHP_EXTENSION macro in php4/aclocal.m4
> around line 420 and you will notice that the script that it expands to checks
> for a directory named along the lines of $abs_srcdir/ext/$1 that wraps the
> whole script segment... there is no php4/ext/ps_mm directory therefore no
> phpext_ps_mm_ptr entry in internal_functions.c is made (latter on by genif.sh).
>
> My comment was (meant to be) that this method of dermining what module entry
> pointers enforces a policy of one module per extension directory (whether this
> policy is intentional or not). Following from this the alternative session
> storage modules (ie ps_mm) break this policy, as they do not have their own
> directory (i.e. ext/ps_mod )
>
> --
> Regards,
>
> Alan van den Bosch
> Sanguis Pty Ltd
>
> Mobile - 0408 106 872
>
> /* All generalizations are false. */
>
> --
> PHP 4.0 Beta Mailing List <http://www.php.net/version4/>
> To unsubscribe, e-mail: php4beta-unsubscribe@lists.php.net
> For additional commands, e-mail: php4beta-help@lists.php.net
> To contact the list administrators, e-mail: php4beta-admin@lists.php.net
>
-Andrei
"When I get a little money, I buy books;
and if any is left I buy food and clothes." -- Erasmus