Hi I like to know why can not the container just use IP address of the client to recongize the client. As IP address is unique. Still does it need to create JSESSIONID?
views:
52answers:
3
+5
A:
IP Address is nowhere near unique.
- It will be the same for people behind a router
- It can change from request to request
- Mobile phones tend to go via the same one
- etc
Noon Silk
2010-01-15 03:10:37
IP address is indeed a unique thing. But what you said further is right.
Adeel Ansari
2010-01-15 03:13:25
Vinegar; that's semantics, it is a "unique thing" obviously; but it can not uniquely identify an end user, which is what he is asking.
Noon Silk
2010-01-15 03:14:32
Also, laptop users who connect to different networks will have different ip addresses and would need to re authenticate.
darren
2010-01-15 03:16:37
...people using multiuser computers...
Tom Hawtin - tackline
2010-01-15 03:28:10
@Vinegar - the only thing that an IP address uniquely identifies is itself.
Stephen C
2010-01-15 05:06:22
+1
A:
If the client's IP changed, what will happen? And how if the client behind the proxy? Then there will be only one ID for all clients behind that proxy.
nanda
2010-01-15 03:10:47
A:
Are you talking about J2EE containers? I think that part of the reason is that HTTP is stateless.
The whole notion of a session is an abstraction that allows you to do more interesting things via HTTP as a sequence of interactions (e.g., shopping cart). Thus, sessions have a unique ID.
While it is common to have one session per IP, it is not rare to have multiple sessions from the same IP (e.g., think of yourself logged in several times to gmail), some IPs are hidden, and it is even possible to have your IP change during the session and use cookies or client memory to retain the session id.
Uri
2010-01-15 03:29:14