MultiThreading should I or shouldn't I?
MultiThreading should I or shouldn't I?
- Subject: MultiThreading should I or shouldn't I?
- From: Ken Tozier <email@hidden>
- Date: Mon, 24 Jun 2002 15:03:55 -0400
MultiThreading sounds catchy and cool, but I have absolutely no
experience with it and don't know the pros and cons. I read the meager
info at Apple and don't know if it would be a good way to go for my app.
I all seems very complex but that may just be due to my complete lack of
experience with multithreading.
Say I want to have realtime streams open to several remote sources of
weather data. Would it be better to have a single bottleneck that the
remote sites log on to or give the remote sources the ability to connect
on their own each spawning a new thread? Could a centralized application
query these threads easily for info? How would it know who's connected
at any given time? Which would be faster?
I'll no doubt have loads more questions but I'll leave it at that for
now.
Thanks
Ken Tozier
P.S. is multithreading on OS X complex enough to justify picking up one
of the tomes on the subject? Any recommended titles?
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.