Matt Monaco wrote:
If you store your login object in a session, when the browser window is
closed the object will automatically be destroyed, thus calling the
destructor.
exactly what is it that triggers the object destruction??? since when is it
normal practice for a browser to do a request
Jochem Maas wrote:
it might be possible to use some browser plugin to hit the server
if it notices that it's window is being closed... although I have a
sneaking
suspicion that Flash, for instance, has the same problem as javascript with
not being able to differentiate between the page
Richard Heyes wrote:
Jochem Maas wrote:
it might be possible to use some browser plugin to hit the server
if it notices that it's window is being closed... although I have a
sneaking
suspicion that Flash, for instance, has the same problem as javascript
with
not being able to differentiate
-Mensagem original-
De: Matt Monaco [mailto:[EMAIL PROTECTED]
Enviada: terça-feira, 29 de Novembro de 2005 0:02
Para: php-general@lists.php.net
Assunto: [PHP] help avoid multiple login
Create an object with the functionality of your choosing, in the destructor
perform your cleanup
De: Matt Monaco [mailto:[EMAIL PROTECTED]
Create an object with the functionality of your choosing, in the destructor
perform your cleanup operations.
The problem is I don't know when a member closes the browser window.
If I knew that i would automatically logout that member.
Thanks.
--
PHP
If you store your login object in a session, when the browser window is
closed the object will automatically be destroyed, thus calling the
destructor.
In response to the message you send directly to me, you would create a file
called Login.class.php and at the top of each page include the
6 matches
Mail list logo
