Alexey is spot on: Session.SessionID.
Why create your own session scheme, when a unique identifier is alerady
created for you by the system? Every time somebody connects, this session ID
is already generated. And, since it is a Globally Unique Identifier (GUID),
it is guaranteed to be unique. If you code your own scheme, you will have to
use GUIDs to guarantee uniqueness as well. Why re-invent the wheel?
If you have a reason you feel you need to create your own session ID, please
post what you are trying to do, from a user perspective, and you will likely
get alternatives to rewriting the ASP.NET session model.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com
*********************************************
Think outside the box!
*********************************************
"bushi" <bu*******@gmail.comwrote in message
news:11**********************@b58g2000hsg.googlegr oups.com...
hi everyone!
i have a web application,i want to get unique session
id for each visitor.session id should not assigned by me like:
session["s_id"]=index;
is it possible to assign a session id automatically when a client
visit my webpage?i will wait 4 any help anxiously as i got stuck at
that point.