Timeline for Long response times vs. concurrency issues on a multithreaded web server
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 4, 2019 at 7:46 | vote | accept | Felix | ||
| Jul 30, 2018 at 10:24 | comment | added | Felix | It may very well be... God I'm in too deep :D Maybe I'll just try to look into it before wasting your time. But thank you very much, I'll investigate and get back. | |
| Jul 30, 2018 at 10:18 | comment | added | Ewan | I have a feeling you may well want more than one of these objects for optimal performance, due to the io constraint. similar to having more than one command window open at the same time. | |
| Jul 30, 2018 at 9:58 | comment | added | Ewan | is it a .net webapi or mvc site? you can use unity DI and registerinstance to instanciate a single object instead of one per request and pass it in through constructor injection on your controllers | |
| Jul 30, 2018 at 9:51 | comment | added | Felix | Thank you for the answer! To my (very limited) knowledge, the classes that handle a request are either instantiated per request, or the methods are some kind of static method e.g. hinted with <Route "foo">. How do I pass it in? | |
| Jul 30, 2018 at 7:59 | history | answered | Ewan | CC BY-SA 4.0 |