Timeline for Multiple Ajax Requests per MVC 4 View
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 22, 2016 at 10:55 | vote | accept | Callum Linington | ||
| Nov 5, 2013 at 16:23 | comment | added | Callum Linington | I believe that when the class has been finished with, it does get disposed of properly, thus the connection gets terminated correctly | |
| Nov 5, 2013 at 14:25 | comment | added | Malachi | when that context class is done it should dispose the connection before another one is even thought about. it might be personal opinion, but I don't like that part of the design, when the object does something, it should open a connection, when it is done it should close that connection. when that object needs to do something (else/again) it should open a completely new connection and close it when it is finished. | |
| Nov 5, 2013 at 12:56 | comment | added | Callum Linington |
Yeah, because the underlying connection gets created on instantiation of the context class, everytime I call that class, transient re instantiates a new copy
|
|
| Nov 4, 2013 at 14:11 | comment | added | Malachi | so you are closing the original connection and then opening a new connection everytime? | |
| Nov 4, 2013 at 12:28 | comment | added | Callum Linington |
Yeah, I took that into account, and started doing InTransientScope() that way it calls up a new connection each time, and it solved all my problems :)
|
|
| Oct 31, 2013 at 19:11 | history | answered | Malachi | CC BY-SA 3.0 |