0

I'm sure like most iOS apps, we have a networking operation that fetches data, one op that parses the data and a CoreData op that stores it and some UI events that display it... each op in it's own thread.

I am trying to figure out a clean approach to track the progress for each full cycle/task, right now I am basically creating a collection of unique ids for each defined cycle which are passed through each thread, it's status is updated when a Notification is sent on success/failure that I listen to, this seems messy.

Is there some type of framework that supports this?

Maybe a design pattern?

Thanks!

Pappy
  • 447
  • 3
  • 15

1 Answers1

1

I think what you are looking for is something like a Finite-state machine.

How to Make a Basic Finite State Machine in Objective-C

Community
  • 1
  • 1
Joe
  • 2,987
  • 15
  • 24
  • I see where you were heading with this, I created something similar. Thanks for pointing me in the right direction. – Pappy May 09 '12 at 19:05