I have a web app that uses SessionManager to handle DO sessions but I also need to off load some work to additional threads. I cannot pass the SessionManager domain to these threads because they don't have access to the HTTPrequest object. I am creating a second domain using the standard Domain.Build which the threads then use to create sessions.

What are the problems with using two domains in the same app?

asked Oct 23 '14 at 00:51

Nomad99's gravatar image


edited Oct 23 '14 at 03:40

One Answer:

Hi Nomad99.

There is no something special in use of two or more domains in single application. I see only one problem - you spend additional time to build second domain.

answered Oct 24 '14 at 03:28

Alexey%20Kulakov's gravatar image

Alexey Kulakov

Also, You may think about building domain into some static field(or property) of class in Global.asax.cs. And then you can give this domain to SessionManager. If you can see this static field from additional threads, then you can use only one domain.

(Oct 24 '14 at 10:11) Alexey Kulakov Alexey%20Kulakov's gravatar image
Your answer
Please start posting your answer anonymously - your answer will be saved within the current session and published after you log in or create a new account. Please try to give a substantial answer, for discussions, please use comments and please do remember to vote (after you log in)!
toggle preview


Once you sign in you will be able to subscribe for any updates here



Asked: Oct 23 '14 at 00:51

Seen: 2,310 times

Last updated: Oct 24 '14 at 10:11

Related questions

powered by OSQA