So instead of having struct arrays, etc, I replace all that with a custom
object, an instance of which represents each process, and manage them by
associating them with different state collections as appropriate.
Thanks, I think that's doable.
_
On 1 Dec 2010, at 3:31 PM, Jon Sigman wrote:
> I have a message receiver which manages a number of TCP-connected processes
> (100
> or so). However, I need to keep track of the state of each connected process
> (registered, busy, waiting, etc) to know what operations are 'legal' or
> appropria
How does one track state in Cocoa?
I have a message receiver which manages a number of TCP-connected processes
(100
or so). However, I need to keep track of the state of each connected process
(registered, busy, waiting, etc) to know what operations are 'legal' or
appropriate for dealing with
