URGENT DOUBT 4 -- SESSION HANDLING

[sanjay sawant]

"behind the scenes, the client’s session id is usually saved on the client in a cookie called JSESSIONID.
For client that don’t support cookies, the session ID can be sent as part of a rewritten URL, encoded using a jsessionid path parameter."

1) If i don't use cookies nor url rewriting can i stil use session management ?
(THIS DOUBT MIGHT SOUND SILLY, BUT I DESPERATELY NEED ANSWER
TO THIS QUESTION....PLEASE HELP ME AS MUCH AS YOU CAN ON QN. 1)

I have read that a session is considered new (isNew() returns true) if
server used only cookie-based sessions, and the client had disabled the use
of cookies, then a session would be new on each request.

[gautam shah]

Originally posted by sanjay sawant:
"behind the scenes, the client’s session id is usually saved on the client in a cookie called JSESSIONID.
For client that don’t support cookies, the session ID can be sent as part of a rewritten URL, encoded using a jsessionid path parameter."

1) If i don't use cookies nor url rewriting can i stil use session management ?
(THIS DOUBT MIGHT SOUND SILLY, BUT I DESPERATELY NEED ANSWER
TO THIS QUESTION....PLEASE HELP ME AS MUCH AS YOU CAN ON QN. 1)

I have read that a session is considered new (isNew() returns true) if
server used only cookie-based sessions, and the client had disabled the use
of cookies, then a session would be new on each request.

ya . there is third kind of session management technique exist named via hidden variable or hidden element or hidden field. but in that case u need a html form on each and every page of ur application. and every request should be submitted through forms only. if u r having any link in that
then just try to append the link with that hidden element by which u want to recognize the session.

i don't think so about isNew(). where u read it ?
although i had not tested but it is very foolish if happening...