Unique browser ID
in [ASP .NET]
|
From: germ on 12 Jan 2010 16:10 not sure what your definition of 'website' is, but 2 'applications' that generate unique sessions when accessed from a single process, even though they may be located at the same root domain are 2 different websites. What Miro stated is correct, ( this is an ASP.NET group is it not ? ) Don't bother to respond - I won't "Scott M." <s-mar(a)nospam.nospam> wrote in message news:O05uxj8kKHA.1824(a)TK2MSFTNGP04.phx.gbl... > > "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 > >
From: Scott M. on 12 Jan 2010 16:38 "germ" <germ2(a)newsgroup.nospam> wrote in message news:%23pT64u8kKHA.3476(a)TK2MSFTNGP06.phx.gbl... > not sure what your definition of 'website' is, but 2 'applications' that > generate unique sessions when accessed from a single process, even though > they may be located at the same root domain are 2 different websites. That's exactly my point. And, as such you can't count on having one session ID that would be the same in all windows/tabs. > What Miro stated is correct, ( this is an ASP.NET group is it not ? ) It's only correct if you are talking about access one site. But, if you were then of course there would only be one session id. > Don't bother to respond - I won't I don't really care if you do or not, I'm still going to correct you. The OP wanted a way to uniquely id a browser from an ASP.NET page. If that browser has tabs already open and engaged with a different site, then the session ID that the OP's site hands out will NOT be able to uniquely id a specific browser on a specific machine, since that browser will now have multiple session ID's in memory from multiple servers. And, as I said, if one domain has multiple applicaitons running on it, the sessions returned by the different applications will not be the same. -Scott > > > > > > "Scott M." <s-mar(a)nospam.nospam> wrote in message > news:O05uxj8kKHA.1824(a)TK2MSFTNGP04.phx.gbl... >> >> "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 >> >> > >
From: Miro on 12 Jan 2010 16:41 Scott, In reference to your quote: > Miro replied that a session ID would be browser specific and not window > specific. This is not true for the reasons I explained. I have a website and when I throw something in the " Session("bla") = date.now if Session("bla") is empty This seems to span accross "ALL" open tabs in my IE when I visit the same page. I seems I do not get a unique Session("bla") per "tab" within IE but I get it per web browser. I get a new Session("bla") date.now when I open the same website in chrome lets say. But If I have IE opened with 1 tab... lets say i get 12noon thrown into the Session("bla") ... if i open another tab within IE... it recognizes that the Session("bla") is not empty so it just spits out the 12noon. If now I open up Google Chrome... i will get lets say 1pm ( in chrome ). But I still seem to get my same Sessions objects accross ALL the tabs within IE when accessing the same website/page. I hope this makes sense. If I did something by coding error - please let me know what to look for... i would like it to act differently per tab. Miro "Scott M." <s-mar(a)nospam.nospam> wrote in message news:O05uxj8kKHA.1824(a)TK2MSFTNGP04.phx.gbl... > > "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 > >
From: Miro on 12 Jan 2010 16:55 Scott, I read your post jsut above >It's only correct if you are talking about access one site. Yes - that is what I was refering to. "The Same Website". I beleive we are in agreement on that fact :-) Cheers' Miro "Miro" <miro(a)beero.com> wrote in message news:e7kY0$8kKHA.5520(a)TK2MSFTNGP06.phx.gbl... > Scott, > > In reference to your quote: >> Miro replied that a session ID would be browser specific and not window >> specific. This is not true for the reasons I explained. > > I have a website and when I throw something in the " Session("bla") = > date.now if Session("bla") is empty > > This seems to span accross "ALL" open tabs in my IE when I visit the same > page. > I seems I do not get a unique Session("bla") per "tab" within IE but I get > it per web browser. > > I get a new Session("bla") date.now when I open the same website in chrome > lets say. > > But If I have IE opened with 1 tab... lets say i get 12noon thrown into > the Session("bla") ... if i open another tab within IE... > it recognizes that the Session("bla") is not empty so it just spits out > the 12noon. > > If now I open up Google Chrome... i will get lets say 1pm ( in chrome ). > > But I still seem to get my same Sessions objects accross ALL the tabs > within IE when accessing the same website/page. > > I hope this makes sense. > > If I did something by coding error - please let me know what to look > for... i would like it to act differently per tab. > > Miro > > > > > "Scott M." <s-mar(a)nospam.nospam> wrote in message > news:O05uxj8kKHA.1824(a)TK2MSFTNGP04.phx.gbl... >> >> "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
|
Pages: 1 2 3 Prev: ReportView + SQLDataSource (dinamically defined) Next: Auto Refresh gridview |