Re: [Phpslash-devel] Using addClassRequirement in PSL 0.7

[Peter C. <pe...@kr...>]

At 16:18 10/02/03 -0600, Joe Stewart wrote:
>On Mon, Feb 10, 2003 at 08:44:22PM +0000, Peter Cruickshank wrote:
>
><snip>
>> 
>> (Have you noticed that $_PSL does in fact end up as a session variable, via $auth->db->psl)?
>>
>
>I think this is corrected in RC2.  RC1 was screwed up this way.
> 
>config.php should be >= 1.30
>
>http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/phpslash/phpslash-ft/public_html/config-dist.php3.diff?r1=1.29&r2=1.30
>
>auth4 has some code to do the "persistent_slots" with php4 sessions.

I'm running auth4.inc rev 1.1 from phplib and am using code based on config-dist.php rev 1.30.

If I stick a print_r($_SESSION) somewhere in my code, $auth->db->psl is included in the output. Or isnt that the same as saying it has been sessionised - is it being re-assigned each time?



>> >The phplib session class using PHP4 sessions currently doesn't
>> >support calling a init script once per session (which is where the
>> >registration of nonessential classes would go).  And with phplib PHP3 
>> >sessions, registering such a large multidimensional variable actually 
>> >slowed down subsequent page calls.  So movement in the sessionizing-$_PSL 
>> >direction stalled.  I think eventually we'll find the right way to get an 
>> >init script working.

I guess having many session variables with identical values for $_PSL cant be very efficient either?

What are the pros & cons of using jpcache to store a common copy of $_PSL - ie one for the whole site, rather than one per active session? (One possible con I can think of is file-locking?)

>If the auto_init was working correctly for phplib I think we would 
>release it.  I'm going to try to get the template path patch applied 
>too.

Cool. 


Peter


-----------------------------
Peter Cruickshank
Tel: +44 7092 086 881
email: pe...@kr...