Timeline for World & client listening, use multi-threading or multi-process?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 28, 2017 at 14:42 | comment | added | Rien | Good point and thanks for the answer, this helped me greatly to get further! | |
| Nov 28, 2017 at 14:33 | vote | accept | Rien | ||
| Nov 28, 2017 at 14:23 | history | edited | Philipp | CC BY-SA 3.0 |
added 225 characters in body
|
| Nov 28, 2017 at 14:16 | history | edited | Philipp | CC BY-SA 3.0 |
added 225 characters in body
|
| Nov 28, 2017 at 14:13 | comment | added | Philipp | @KrijnvanderBurg By the way, you might want to tag your questions with the technologies you are using. Best practices vary a lot depending on your framework. | |
| Nov 28, 2017 at 14:12 | comment | added | Philipp | @KrijnvanderBurg When you are using Java, then you should use the New-IO API. It's a great API for handling a large number of clients without having to use multithreading. | |
| Nov 28, 2017 at 14:11 | history | edited | Philipp | CC BY-SA 3.0 |
added 225 characters in body
|
| Nov 28, 2017 at 14:08 | comment | added | Rien | Good point about the system platform but im developing in java for all OS systems, not a specific one. Is what you suggest by using the system API's still viable / possible then? | |
| Nov 28, 2017 at 14:00 | history | edited | Philipp | CC BY-SA 3.0 |
added 1 character in body
|
| Nov 28, 2017 at 13:55 | history | answered | Philipp | CC BY-SA 3.0 |