Timeline for How is multi-threading different in a Java based Web Application vs Stand-alone Java Application
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14, 2021 at 19:36 | comment | added | Michael Borgwardt | @kaushalpranav: The alternative would be using an event-based API like Java's nio (like Netty does). And what does "best" or "better" mean? Event-based APIs tend to be able to handle more overall requests, but also less intuitive and thus more error prone. But this can change with different implementations and versions. | |
| May 14, 2021 at 16:28 | comment | added | kaushalpranav | In the last para, when you said "... might be you need to access other network resources, e.g. call several different web services ..." - is creating a new thread for every webservice call the best possible way ? Or is there someother better way to handle calling multiple requests ? Thanks :) | |
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Jun 12, 2013 at 15:46 | vote | accept | kapricanon | ||
| Jun 12, 2013 at 13:54 | history | edited | Michael Borgwardt | CC BY-SA 3.0 |
deleted 1 characters in body
|
| Jun 12, 2013 at 13:53 | comment | added | Michael Borgwardt | @kapricanon: yes, unless you have some specific requirements it can't handle, or your web server already has something similar. | |
| Jun 12, 2013 at 13:30 | comment | added | kapricanon | Makes sense. Is ExecutorService Interface the best way to go about creating new threads in a web application? | |
| Jun 12, 2013 at 13:14 | history | answered | Michael Borgwardt | CC BY-SA 3.0 |