It would certainly require cookies. I'm not sure I'd be too worried about
people that didn't have them turned on. They'd be making a choice about
cookies vs ease of use, which seems acceptable. They'll just have to login
multiple times.
Perhaps it would be something where the first time the user ever logs in,
all the cookies get set as I mentioned before (again, they just set a unique
key and nothing else). Then in the future when a visitor comes to a site, a
script checks for that cookie and if it's present, checks the db to see if
they've been logged in. If so, it just transparently sets a cookie saying
they're logged in to that particular site as the page is being displayed.
If the cookie is not present (which could be for several reasons) then
they're required to login anyway and we reset the cookies as in step 1. But
the point is that the unique id cookies are persistent so once they had been
set you shouldn't have to go through the cycle of setting them all again.
There are problems with this too, but I guess I'm thinking through the
problem, hoping others will have some ideas as well. It doesn't seem like
it should be impossible, though it may turn out to be impractical.
"Aaron Bertrand - MVP" <aa***@TRASHaspfaq.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
This seems pretty kludgey though,
Yes, because as you add "related sites" this process will take longer and
longer. There is also no guarantee that the user will leave the popup
window long enough for all the sites to get registered, nor are you
guaranteed that they have scripting and/or cookies enabled, etc etc