phpwebsite-developers

[Phpwebsite-developers] phpWhosOnline

[Todd O. <to...@da...>]

Does everyone plan to use this module (which I think is neat by the way)?

I'm asking because the Roadmap is to use native php4 sessions.  However, if
most everyone plans to use this module, we may want to reconsider using a
database backed session object like ezPublish has.  Thoughts?

--Todd

Re: [Phpwebsite-developers] phpWhosOnline

[Karsten D. <k.d...@tu...>]

On Tue, Apr 24, 2001 at 09:46:20PM -0400, Todd Owen wrote:
> Does everyone plan to use this module (which I think is neat by the way)?
>=20
> I'm asking because the Roadmap is to use native php4 sessions.  However, =
if
> most everyone plans to use this module, we may want to reconsider using a
> database backed session object like ezPublish has.  Thoughts?

That does in no way contradict! You can register custom session data
storage containers with the native PHP4 sessions. So you can count the
records, and still use the natvive sessions. No problem :-)

Regards,
Karsten
--=20
Why do we have to hide from the police, daddy?
Because we use emacs, son. They use vi.
-----------------------------
mailto:k.d...@tu... w=B3: http://www.k-fish.de/
gpg: http://www.k-fish.de/mykeys.gpg

Re: [Phpwebsite-developers] phpWhosOnline

[Todd O. <to...@da...>]

Karsten wrote:
> That does in no way contradict! You can register custom session data
> storage containers with the native PHP4 sessions. So you can count the
> records, and still use the natvive sessions. No problem :-)

You can indeed select an alternative to /tmp/ file storage of session_id's
in PHP4 using the native session routines.  However, this requires access to
the php configuration files, which many web hosting companies don't offer.
Furthermore, you don't get the flexibility (in my opinion) of a session
class you design yourself.

--Todd

Re: [Phpwebsite-developers] phpWhosOnline

[Richard R. <rr...@sh...>]

On Wednesday 25 April 2001 13:14, you wrote:
> Karsten wrote:
> > That does in no way contradict! You can register custom session data
> > storage containers with the native PHP4 sessions. So you can count the
> > records, and still use the natvive sessions. No problem :-)
>
> You can indeed select an alternative to /tmp/ file storage of session_id's
> in PHP4 using the native session routines.  However, this requires access
> to the php configuration files, which many web hosting companies don't
> offer. Furthermore, you don't get the flexibility (in my opinion) of a
> session class you design yourself.

Agreed.  Making PHPWebsite depend on third party libraries or require changes 
to the global php or apache config files are (IMHO) bad ideas.

_________________________
Richard Rowell
rr...@sh...

If Java had true garbage collection, most programs would delete themselves 
upon execution. - Robert Sewell 

Re: [Phpwebsite-developers] phpWhosOnline

[Karsten D. <k.d...@tu...>]

On Wed, Apr 25, 2001 at 02:14:28PM -0400, Todd Owen wrote:
> Karsten wrote:
> > That does in no way contradict! You can register custom session data
> > storage containers with the native PHP4 sessions. So you can count the
> > records, and still use the natvive sessions. No problem :-)
>=20
> You can indeed select an alternative to /tmp/ file storage of session_id's
> in PHP4 using the native session routines.  However, this requires access=
 to
> the php configuration files, which many web hosting companies don't offer.
> Furthermore, you don't get the flexibility (in my opinion) of a session
> class you design yourself.

That is not what I meant, changing the session save path is in no way
a great improvement in fexibility. I was referring to the following
function and it's possibilities:

void session_set_save_handler   (string open, string close, string read, st=
ring write, string destroy, string gc)

See some of the native sessions tutorials at all those developer sites
for some more on that. It gives you all the flexibility you need and
still makes it possible to use the fast and easy session handling
provided by PHP4

And you don't need access to any configuration file (that does apply
to other settings as well, there are ini_set and ini_alter).

Regards,
Karsten
--=20
Why do we have to hide from the police, daddy?
Because we use emacs, son. They use vi.
-----------------------------
mailto:k.d...@tu... w=B3: http://www.k-fish.de/
gpg: http://www.k-fish.de/mykeys.gpg

RE: [Phpwebsite-developers] phpWhosOnline

[Alain F. <al...@va...>]

Hi,

That's what I thought too, but I checked the doc first before I was about to
post the same message as you did... unfortunately, you DO need access to the
configuration file, because you need to tell PHP not to use the normal
'file' session handlers, but your own 'user' session handlers. And that
needs to be set in php.ini.

As for ini_set() and so on, I suppose most PHP hosting companies would
disable that function for security reasons.

> -----Message d'origine-----
> De : php...@li...
> [mailto:php...@li...]De la part de
> Karsten Dambekalns
> Envoyé : jeudi 26 avril 2001 11:29
> À : php...@li...
> Objet : Re: [Phpwebsite-developers] phpWhosOnline
>
>
> [cut]
>
> void session_set_save_handler   (string open, string close,
> string read, string write, string destroy, string gc)
>
> See some of the native sessions tutorials at all those developer sites
> for some more on that. It gives you all the flexibility you need and
> still makes it possible to use the fast and easy session handling
> provided by PHP4
>
> And you don't need access to any configuration file (that does apply
> to other settings as well, there are ini_set and ini_alter).
>
> Regards,

Re: [Phpwebsite-developers] phpWhosOnline

[Karsten D. <k.d...@tu...>]

On Thu, Apr 26, 2001 at 12:09:35PM +0200, Alain Fontaine wrote:

> That's what I thought too, but I checked the doc first before I was about=
 to
> post the same message as you did... unfortunately, you DO need access to =
the
> configuration file, because you need to tell PHP not to use the normal
> 'file' session handlers, but your own 'user' session handlers. And that
> needs to be set in php.ini.

Damn! I knew I would expose myself to laughter one day :-) But that is
indeed bad news. I didn't think about that (having your own server
makes life easier...).

> As for ini_set() and so on, I suppose most PHP hosting companies would
> disable that function for security reasons.

Well, are there any stats regarding that? Any experience anyone? And
what about .htaccess? Some hosters might let you use that. And last
not least they could check, right?

And what about those who want to set up a multiple organisation (read
big) phpWSII installation? I would think they have access to some
decent hosting environment... It can be bad to avoid using better
techniques just for the sake of some "standard home user". After all:
What is our target audience? Didn't see that in the roadmap :-)
Honestly, who shall be using phpWSII when it is ready and what can we
expect them to have on their server? Just PHP4? Or even some power? Or
root privileges? This is something we should think about, I guess.

In the end: Wouldn't it be possible to use files for session data per
default and let the user choose (if possible) to use a DB instead, if
he wanted/needed the features that provides? User John Doe, with his
100 hits per month would do good _not_ to enable a whosonline display
(it would read 1 visitor most of the time), and when it becomes
interesting to know the number of visitors you probably have enough
power over your server to enable user session handlers. (See my post
about the roadmap for another example of user choice: mailing lists.)

Just my 2 cents,
Karsten
--=20
Why do we have to hide from the police, daddy?
Because we use emacs, son. They use vi.
-----------------------------
mailto:k.d...@tu... w=B3: http://www.k-fish.de/
gpg: http://www.k-fish.de/mykeys.gpg

[Phpwebsite-developers] Something to look at ...

[clayton c. <cc...@ca...>]

this just showed up at Hotscripts :

http://www.unica.edu/uicfreesoft/php-js-webedit/info_php-js-webedit_eng.html


looks very interesting ....

clayton

Re: [Phpwebsite-developers] Something to look at ...

[Jason C. <cam...@xp...>]

Thats pretty interesting!  I've seen something else floating around similar 
to that, it might of been on hotscripts too.  Not too sure where I seen it, 
maybe SourceForge.

> this just showed up at Hotscripts :
> 
> http://www.unica.edu/uicfreesoft/php-js-webedit/info_php-js-
webedit_eng.html
> 
> 
> looks very interesting ....
> 
> clayton
> 
> 
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers


-- 
Jason Campbell
Xplozive Media Technologies
www.xplozivemedia.com
phpWebSite Developer