Unique browser ID
in [ASP .NET]
|
From: germ on 12 Jan 2010 12:42 huh ? what browsers/os are you referring to ? all of the most popular ( ie, ff , op , ... ) current version browsers running on windows create just one session per machine regardless of the number of browser windows you have open - exactly the opposite to what you just stated. "Scott M." <s-mar(a)nospam.nospam> wrote in message news:OQwxFw6kKHA.5520(a)TK2MSFTNGP06.phx.gbl... > > "Miro" <miro(a)beero.com> wrote in message > news:O1uN%23b6kKHA.3476(a)TK2MSFTNGP06.phx.gbl... >>I beleive the closest you can get is just get the Session - and that is >>browser specific, >> but not window specific ( within the browser ) >> >> M. > > Actually, session ID's are issued by the server, and so, they are not > browser-specific. In fact, they have more to do with the browser window > than they do with the browser application, since one session cannot span > multiple browser windows, but one browser could have many sessions going > simultaneously. > > -Scott >
From: germ on 12 Jan 2010 12:51 I take that back ( partly ) this is true for ie but does not apply to non-ms browsers and does not apply to multiple tabs even in IE "germ" <germ2(a)newsgroup.nospam> wrote in message news:%23v0bM66kKHA.2184(a)TK2MSFTNGP04.phx.gbl... > huh ? > what browsers/os are you referring to ? > all of the most popular ( ie, ff , op , ... ) current version browsers > running on windows create just one session per machine regardless of the > number of browser windows you have open - exactly the opposite to what you > just stated. > > > > > "Scott M." <s-mar(a)nospam.nospam> wrote in message > news:OQwxFw6kKHA.5520(a)TK2MSFTNGP06.phx.gbl... >> >> "Miro" <miro(a)beero.com> wrote in message >> news:O1uN%23b6kKHA.3476(a)TK2MSFTNGP06.phx.gbl... >>>I beleive the closest you can get is just get the Session - and that is >>>browser specific, >>> but not window specific ( within the browser ) >>> >>> M. >> >> Actually, session ID's are issued by the server, and so, they are not >> browser-specific. In fact, they have more to do with the browser window >> than they do with the browser application, since one session cannot span >> multiple browser windows, but one browser could have many sessions going >> simultaneously. >> >> -Scott >> > >
From: Scott M. on 12 Jan 2010 14:24 "germ" <germ2(a)newsgroup.nospam> wrote in message news:%23v0bM66kKHA.2184(a)TK2MSFTNGP04.phx.gbl... > huh ? > what browsers/os are you referring to ? Any and all of them. > all of the most popular ( ie, ff , op , ... ) current version browsers > running on windows create just one session per machine regardless of the > number of browser windows you have open - exactly the opposite to what you > just stated. Uh no. A Session is server object which represents a "conversation" taking place between a client and that server. Whenever a client (any client) connects to a server that utilizes sessions, the server looks at the HTTP request header to see if a session is referenced. If not, the server generates a new session object and assigns a unique session ID to that object. In addition, when the server sends down the response to the client, the HTTP response header will include this session ID, which the client then stores and will place into the next HTTP request header going back to that server/domain. Since a browser can have many windows/tabs open and each window/tab can be getting content from completely unrelated servers/domains, sessions are not shared across windows/tabs of a client and one browser instance can very well be participating in several server sessions. This simplest example of this would be to log on to two different online banking sites using two different tabs of the same browser instance. Once you log into to each bank site, you'll have two different and distinct sessions going - one with each bank site. Since sessions are managed by the server, not the client, each bank site is free to log you off after its own pre-determined time of inactivity. Again, sessions are not managed by the client and a client can have many sessions going at once, but sessions are not shared across windows/tabs of a client. This is true for all clients. -Scott > > > > > "Scott M." <s-mar(a)nospam.nospam> wrote in message > news:OQwxFw6kKHA.5520(a)TK2MSFTNGP06.phx.gbl... >> >> "Miro" <miro(a)beero.com> wrote in message >> news:O1uN%23b6kKHA.3476(a)TK2MSFTNGP06.phx.gbl... >>>I beleive the closest you can get is just get the Session - and that is >>>browser specific, >>> but not window specific ( within the browser ) >>> >>> M. >> >> Actually, session ID's are issued by the server, and so, they are not >> browser-specific. In fact, they have more to do with the browser window >> than they do with the browser application, since one session cannot span >> multiple browser windows, but one browser could have many sessions going >> simultaneously. >> >> -Scott >> > >
From: germ on 12 Jan 2010 15:27 True for 2 different sites ( and why would you care ) but this does not hold true for two tabs or windows ( non-ie ) with connections to the SAME site which is what I assume the was referring as this is am extremely common question. "Scott M." <s-mar(a)nospam.nospam> wrote in message news:ugz$Hz7kKHA.2184(a)TK2MSFTNGP04.phx.gbl... > > "germ" <germ2(a)newsgroup.nospam> wrote in message > news:%23v0bM66kKHA.2184(a)TK2MSFTNGP04.phx.gbl... >> huh ? >> what browsers/os are you referring to ? > > Any and all of them. > >> all of the most popular ( ie, ff , op , ... ) current version browsers >> running on windows create just one session per machine regardless of the >> number of browser windows you have open - exactly the opposite to what >> you just stated. > > Uh no. A Session is server object which represents a "conversation" > taking place between a client and that server. Whenever a client (any > client) connects to a server that utilizes sessions, the server looks at > the HTTP request header to see if a session is referenced. If not, the > server generates a new session object and assigns a unique session ID to > that object. In addition, when the server sends down the response to the > client, the HTTP response header will include this session ID, which the > client then stores and will place into the next HTTP request header going > back to that server/domain. > > Since a browser can have many windows/tabs open and each window/tab can be > getting content from completely unrelated servers/domains, sessions are > not shared across windows/tabs of a client and one browser instance can > very well be participating in several server sessions. > > This simplest example of this would be to log on to two different online > banking sites using two different tabs of the same browser instance. Once > you log into to each bank site, you'll have two different and distinct > sessions going - one with each bank site. Since sessions are managed by > the server, not the client, each bank site is free to log you off after > its own pre-determined time of inactivity. > > Again, sessions are not managed by the client and a client can have many > sessions going at once, but sessions are not shared across windows/tabs of > a client. This is true for all clients. > > -Scott > >> >> >> >> >> "Scott M." <s-mar(a)nospam.nospam> wrote in message >> news:OQwxFw6kKHA.5520(a)TK2MSFTNGP06.phx.gbl... >>> >>> "Miro" <miro(a)beero.com> wrote in message >>> news:O1uN%23b6kKHA.3476(a)TK2MSFTNGP06.phx.gbl... >>>>I beleive the closest you can get is just get the Session - and that is >>>>browser specific, >>>> but not window specific ( within the browser ) >>>> >>>> M. >>> >>> Actually, session ID's are issued by the server, and so, they are not >>> browser-specific. In fact, they have more to do with the browser window >>> than they do with the browser application, since one session cannot span >>> multiple browser windows, but one browser could have many sessions going >>> simultaneously. >>> >>> -Scott >>> >> >> > >
From: Scott M. on 12 Jan 2010 15:51 "germ" <germ2(a)newsgroup.nospam> wrote in message news:uHMOqW8kKHA.2780(a)TK2MSFTNGP05.phx.gbl... > True for 2 different sites ( and why would you care ) but this does not > hold true for two tabs or windows ( non-ie ) with connections to the SAME > site which is what I assume the was referring as this is am extremely > common question. It may be an common question, but it does not have a clear answer as I have been trying to explain. The OP has asked: "Is there a way to retrieve a unique identifier for a client browser instance, from within an ASP.NET page?". Miro replied that a session ID would be browser specific and not window specific. This is not true for the reasons I explained. In addition, in enterprise environments, one site may have several applications running within it and spawn a new window to that new application(even though the visitor is still at the same "site") from a hyperlink click, in which case a NEW session will be created. The fact is that you cannot count on a single session to uniquely identify one tab or window in a browser, even when one web "site" is involved because that one web site may be running more than one web application. And, don't forget about Session Cookies, wich operate differently and often get mixed up with server Session objects. Also, what about cookie-less sessions offered by ASP .NET? Now, the situation changes again. -Scott
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 Prev: ReportView + SQLDataSource (dinamically defined) Next: Auto Refresh gridview |