I ran into a problem where I had an Html.DropDownList in my view that would postback the selected value the first time I submitted the form, but each subsequent postback would only post data from the initial postback. So I added lifestyle="transient" to the component element where I had configured my controller for castle windsor, which fixed the problem, but of course made postbacks take longer since a new controller was being instantiated per request. Given the information above, what insight, suggestions, or solutions might help determine my original question about the controller lifestyle? Thanks for all the help and support!
views:
172answers:
1
+1
A:
MVC controllers are transient. Thinking about it, this makes sense for a few reasons. First, if a single instance is used to service multiple requests and if multiple requests happen to hit the same controller at the same time, you're going to experience some fairly bizarre race conditions. Second, HTTP is by its very nature stateless, and requests exist independently of one another. This is reflected in the transient lifestyle of controllers.
Levi
2009-11-24 19:16:49
LOL. I was probably overthinking that one without considering that at all. Thanks for the insight. Probably and obvious YES to my question, but I was thinking too much inside the windsor box to realize the solution. Thank you very much!
mkelley33
2009-11-24 20:15:45