To thread or not to thread?
To thread or not to thread?
- Subject: To thread or not to thread?
- From: Ulrich Bauer <email@hidden>
- Date: Sun, 16 Feb 2003 18:15:00 +0100
Hi List,
I have a very general question: I am working on a distributed text
editor that currently uses one thread for everything, i.e. one runloop
for keyboard events as well as network i/o. Now I've realized that at
the moment some runloop modes (selecting text) prevent the network
events from getting through and thus the socket buffer may run full.
So what is your opinion: Is it better to introduce a designated thread
for handling network events or to try to ensure that no operation or
mode blocks the runloop for too much time?
Thanks for your answers,
--
Ulrich Bauer Mail: email@hidden
Lehrstuhl f|r Angewandte Softwaretechnik Tel.: +49 (89) 289-18240
Institut f|r Informatik Raum: 01.07.039
Technische Universitdt M|nchen PGP ID: 0361C54B
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.