[snip]
If you give the session a custom name, then, yes, you'll have to use that
name on every page. $name can be something that in an include file or a
constant, etc, though. Again, you don't _have_ to give a name, though.
There's no real advantage to using another name, though, as it's going to
Andy B mailto:[EMAIL PROTECTED]
on Monday, March 22, 2004 3:19 PM said:
so the theory is: if i require that the session be named after the
persons login name there is probably 1 out of 2 million chances that
it will mess up the names and get confused (specially if there are
only a few
What are the chances of two people getting the same session number in a
thousends of day operation?
When you down the size of that to a couple hundeed a day...
WHy do we need to have a session name for that?
Vamp
Chris W. Parker [EMAIL PROTECTED] escribió en el mensaje
news:[EMAIL PROTECTED]
as long as your usernames are unique you should never have a problem.
(assuming everything else works as planned.)
it should...
i want to use sessions for a login system and stuff too but i want it to
check to see if the person is logged in before going to the login section...
if the session
What are the chances of two people getting the same session number in a
thousends of day operation?
When you down the size of that to a couple hundeed a day...
WHy do we need to have a session name for that?
because eventually i want to take the user name (session name/variables/user
info) and
Elliot J. Balanza mailto:[EMAIL PROTECTED]
on Monday, March 22, 2004 3:43 PM said:
What are the chances of two people getting the same session number in
a thousends of day operation?
When you down the size of that to a couple hundeed a day...
WHy do we need to have a session name for
Andy B mailto:[EMAIL PROTECTED]
on Monday, March 22, 2004 3:43 PM said:
as long as your usernames are unique you should never have a problem.
(assuming everything else works as planned.)
it should...
it will. a unique value is a unique value.
is this code valid??
?php
Andy B mailto:[EMAIL PROTECTED]
on Monday, March 22, 2004 3:49 PM said:
because eventually i want to take the user name (session
name/variables/user info) and create a preferences section of the
website im doing and that would require a constant session name from
visit to visit
yeah
you've already got that unique identifier. it's the username. the
username will stay unique visit to visit, therefore you don't need to go
against the design of the session id. the session id is not meant to
keep uniqueness across multiple visits, only the current visit.
are we/me
Andy B wrote:
as long as your usernames are unique you should never have a problem.
(assuming everything else works as planned.)
it should...
i want to use sessions for a login system and stuff too but i want it to
check to see if the person is logged in before going to the login section...
if
Andy B wrote:
WHy do we need to have a session name for that?
because eventually i want to take the user name (session name/variables/user
info) and create a preferences section of the website im doing and that
would require a constant session name from visit to visit
Ummm... that's why you set a
Andy B wrote:
[snip]
If you give the session a custom name, then, yes, you'll have to use that
name on every page. $name can be something that in an include file or a
constant, etc, though. Again, you don't _have_ to give a name, though.
There's no real advantage to using another name, though, as
Andy B wrote:
you've already got that unique identifier. it's the username. the
username will stay unique visit to visit, therefore you don't need to go
against the design of the session id. the session id is not meant to
keep uniqueness across multiple visits, only the current visit.
are
On 22 Mar 2004 Andy B wrote:
so the theory is: if i require that the session be named after the persons
login name there is probably 1 out of 2 million chances that it will mess up
the names and get confused (specially if there are only a few users
allowed)...
If the login name is unique and
14 matches
Mail list logo
