So basically I want to set a cookie that will allow them to enter the site
under their userid, but I can't allow them to enter if they are currently
logged in from elsewhere.
Any ideas?
I use cookie-based auth in a few places, with a "can be logged in
only once" restriction, but I duck the
Is there anyway to know that a user has disconnected from their session
through network failure, power off, or browser closure? I am logging
information about the user to a database when they login to a site, and
I need to clean up this data when they leave. Obviously this is no
problem with
Hi Trey!
Is there anyway to know that a user has disconnected from their session
through network failure, power off, or browser closure?
How about extracting the user's IP address and then, if he hasn't sent
anything over for a time period, ping him?
-- Craig (The Data Ferret)
Yeah, thought about that, but that won't work if they are sitting behind a
firewall.
Trey
Craig E Ransom wrote:
Hi Trey!
Is there anyway to know that a user has disconnected from their session
through network failure, power off, or browser closure?
How about extracting the user's IP
At 03:00 PM 11/20/00 -0600, Trey Connell wrote:
Is there anyway to know that a user has disconnected from their session
through network failure, power off, or browser closure?
How is that different from just going out for a cup of coffee or opening a
new browser window and looking at a
On Mon, 20 Nov 2000, Bill Moseley wrote:
At 03:00 PM 11/20/00 -0600, Trey Connell wrote:
Is there anyway to know that a user has disconnected from their session
through network failure, power off, or browser closure?
How is that different from just going out for a cup of coffee or
Well, this is the basic scenario.
The same userid cannot be logged into the app more than once at any given
time. Also, we want to use a cookie to keep the user from having to explicitly
login everytime.
The latter will be accomplished with cookies and the first rule will be
enforced with a
At 05:20 PM 11/20/00 -0600, Trey Connell wrote:
The latter will be accomplished with cookies and the first rule will be
enforced with a "loggedin" flag in the database. My problem lies in the user
not explicitly clicking logout when they leave the site. If they explicitly
click logout, i can
Trey Connell writes:
Well, this is the basic scenario.
The same userid cannot be logged into the app more than once at any given
time. Also, we want to use a cookie to keep the user from having to explicitly
login everytime.
Just some random ideas, not necessarily the ideal solution:
Yeah, big troubleI'm thinking the client's just retarded. ;~)
Bill Moseley wrote:
At 05:20 PM 11/20/00 -0600, Trey Connell wrote:
The latter will be accomplished with cookies and the first rule will be
enforced with a "loggedin" flag in the database. My problem lies in the user
not
10 matches
Mail list logo
