Session Sharing Across the domain

  • Thread starter Thread starter Suresh
  • Start date Start date
Hi,

store session data with SessionStateMode set to StateServer if performance
is important, or set it to SQLServer if reliability is your main concern.

regards
Joyjit
 
Hi ,

Thanks for Reply,

Problem here is I want to share the session state between ASP and ASP.Net
across the domains. In more clearer, ASPX pages are under abc.com domain and
ASP Pages are under xyz.com domain. I want to call an ASP page which is
under xyz.com from ASPX page that is under abc.com by persisting the state
information.

Thanks
Suresh
 
Hi,

We have tried that aproach. That article works fine only when both ASP and
ASPX pages are under the same domain. It doesn't work when the pages are
under different domains.

Thanks
Suresh
 
Suresh said:
Hi,

We have tried that aproach. That article works fine only when both ASP and
ASPX pages are under the same domain. It doesn't work when the pages are
under different domains.
Click to expand...

Suresh, can you share cookies between these two domains? If not, then you
won't be able to share session state, either.

John Saunders
 
Hi,

Cookies cannot be shared between the domains. That is right. But we need to
share the session between two different domains. This is mandatory. I would
like to know any other aproaches to make it done. We have found some other
alternaives thru which we can make it done. But it drastically reduces the
performance.

Is there any thrid party tools that can serve this purpose (Session State
Sharing between the domains)

Thanks
Suresh.
 
Suresh said:
Hi,

Cookies cannot be shared between the domains. That is right. But we need
to
share the session between two different domains. This is mandatory. I
would
like to know any other aproaches to make it done. We have found some other
alternaives thru which we can make it done. But it drastically reduces the
performance.

Is there any thrid party tools that can serve this purpose (Session State
Sharing between the domains)
Click to expand...

This means that you'll have to use cookie-less sessions. See the
documentation on the <sessionState> element in the web.config file.

John Saunders
 
documentation on the <sessionState> element in the web.config file can not
help to solve this problem

Suresh
 
Suresh said:
documentation on the <sessionState> element in the web.config file can not
help to solve this problem
Click to expand...

It helps with the idea of cookieless sessions. Is something more required to
solve this problem? If the sessions don't use cookies, then I don't know why
they would be sensitive to the domain. They would still be sensitive to
application boundaries, perhaps, but not to the domain.

John Saunders
 
Back
Top