Have Geek Brain

Best Practice for LINQ to SQL Object Resilience Between ASP.NET Queries

In my current project I am using LINQ to SQL as ORM. For now, I keep the changed entities in the session to keep the changes made between ASP.NET requests. What's the best practice for doing this, because lately I've started using this approach, not very scalable for web farms.

0


a source to share


2 answers


I personally wouldn't do that at all. I know it is possible to reattach entities, but this is not trivial and I am sincerely trying my best to figure out how this can be done with other methods of maintaining state.



There is a good article here that says there are pros and cons of different methods, but I would be interested to know,

+2


a source


Do you mean this isn't scaling for your web farm because you have an InProc session or because the more general process doesn't scale? My opinion would be that if you have an InProc session and therefore will not work through the web farm, then you would have to abandon the process somewhere to store this data and you could also commit the database ... But, if you have a special circumstance, you can explain it to get a better answer.



0


a source






More articles:


All Articles