Home/ Questions/Q 8046153
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-05T05:43:12+00:00

Framework: ASP.Net MVC 3 When a request comes in, I am intercepting the request

  • 0

Framework: ASP.Net MVC 3

When a request comes in, I am intercepting the request through a global filter and performing a database look up based on the subdomain. The return int from the DB lookup needs to be persisted to other objects (i.e. Controllers) so that the DB hit doesn’t need to be performed again whenever that data might be needed.

I was hoping to avoid using cookies since this information is a pertinent part of the system and I didn’t want to rely on cookies being enabled.

I have read the related questions here and here which have not provided any good answers.

I actually have two questions:

  1. As of now I had come up with a Subdomain manager object which does the heavy lifting and through my IoC have the manager object be HTTP Request scoped and I can grab that manager anytime during the request as a possible solution.

    Is there a better way to carry this information across different object in the MVC request pipeline after I have looked it up? – I had examined the idea of putting the information back into the request somehow (which pertains to question #2).

  2. If you were to use the Request to store the data (i.e. intercept the request, perform look up, write to the request) where would be the logical place to hold that information?

    I reviewed the session but this seems to be closely tied to the way the web server is configured for sessions and I already mentioned I don’t want to use cookies. Other areas such as post data and query string collections are locked down for their security reasons.

Any suggestions?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    1 Is pretty close.

    Your SubDomain manager could probably be a singleton (using your IOC container perhaps), with a simple static Dictionary for looking up a subdomain once the data has been initially loaded. If you are concerned about having this initial load occur and be syncd across several servers without executing the data load multiple times you could look at a distributed cache (appfabric, ncache, memcache) depending on the overhead of making the DB call.

    I would not use HttpContext.Item to store the Id however. I would use your IOC container to Inject this into your controller(s) (Property inject probably). Using most IOC containers you should be able to have this fire on the start of a HttpRequest and last last the lifetime of the “User Session/Transaction”.

    NHibernate Burrows allows all of this to be implemented so easily it’s laughable http://nhforge.org/wikis/burrow/default.aspx

    • 0