Home/ Questions/Q 6950331
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T14:04:46+00:00

I’ve been fighting and fighting for some time with a decent way to handle

  • 0

I’ve been fighting and fighting for some time with a decent way to handle a workflow based on a series of asynchronous ASIHTTPRequests (I am using queues). So far it seems to have eluded me and I always end with a hideous mess of delegate calls and spaghetti code exploding all over my project.

It works as follows:

  1. Download a list of items (1 single ASIHTTPRequest, added to a queue).
  2. The items retrieved in step 1 need to be stored.
  3. Each item, from 1 is then parsed, queuing a 1 ASIHTTPRequest per item, for it’s sub-items.
  4. Each of the requests from step 3 are processed and the sub-items stored.

I need to be able to update the UI with the progress %age and messages.
I’m unable for the life of me to figure out a clean/maintainable way of doing this.

I’ve looked at the following links:

But either I’m missing something, or they don’t seem to adequately describe what I’m trying to achieve.

Could I use blocks?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I see myself facing a quite similar issue as I got the exercise to work on a app using a set of async http and ftp handlers in a set of process and workflows.
    I’m not aware about ASIHTTP API but I assume I did something similar.
    I defined a so called RequestOperationQueue which can for example represent all request operations of a certain workflow. Also I defined several template operations for example FTPDownloadOperation. And here comes the clue. I implemented all these RequestOperations more or less accroding to the idea of http://www.dribin.org/dave/blog/archives/2009/05/05/concurrent_operations/. Instead of implementing the delegate logic in the operation itself I implemented sth like callback handlers specialized for the different protocols (http, ftp, rsync, etc) providing a status property for the certain request which can be handled by the operation via KVO.
    The UI can be notified about the workflow for example by a delegate protocol for RequestOperationQueue. for example didReceiveCallbackForRQOperation:(RequestOperation) rqo.
    From my point of view the coding of workflows including client-server operations gets quite handy with this approach.

    • 0