fivesquaresoftware/restclient

Simple, powerful HTTP client for Cocoa+REST geeks

restclient's Issues

Make RCResource <NSCoding>

You could store an entire configuration of resources to disk if you wanted ...

Make individual requests cancelable

Currently you can only cancel all requests fired for a resource instance. A caller might want more control, for example if a number of requests for the same resource came in all at once and one wanted to keep one alive and cancel the rest.

This will involve returning a token to the caller of the async request methods that can be used to cancel the request as desired.

Add request groups to allow for tracking heterogeneous request clusters

We want to simplify tracking the completion of groups of related requests, which may or may not be for the same resource. Propose we do this by creating RCRequestGroup or something similar that allows callers to register a block that gets run when all the requests in the group are complete.

For example,

[RCRequestGroup withCompletionHandler:^{ <foo> }];

and, we can allow a collection of blocks as well, in addition to setting a flag as to whether they get removed when the group hits zero requests:

[group addCompletionHandler:^{ <foo> } clearWhenDone:YES];

Add support for fixtures

Add support to RCResource so that it can return data from a fixture (.plist) instead of actually running a request. This could be accomplished a couple ways:

[resource addFixture:someObject];
[resource addFixtureNamed:@"Foo.plist"];

We could also have a top-level interface:

[RESTClient loadFixtures:@"Foo.plist"]
[RESTClient userFixtures:NO];

The fixture file in this case could have a list of fixtures for each resource:

<key>http://example.com</key>
<dictionary>...</dictionary>

Let encoding be figured out by file extension if it hasn't been set

Add the ability to scope a request, so when the scope goes away a request can automatically cancel

Expose the request queue from RCResource so a caller can set up their own queues.

Currently when a resource runs a request, it's using the main thread's runloop (instead of the NSOPQ based methods that were new in iOS5) to run the request because of bugs in the NSOpQ.

Confirm the bugs are fixed and run the request on the main Q or a supplied external Q. Also, allow the post-processing Q to be set from outside the request as well. It's currently just using a global concurrent Q.

Custom Username Header

Make RCResource be <NSCopying>

In case you want to use a resource as a key in a collection

autorelease without pool

There's a bunch of class +load methods which uses autoreleased objects. The problem is, as seen here [1], that there's no autorelease pool yet when +load is being called. You need to either:

• use +initialize instead
• or surround the code with @autoreleasepool { }

[1] http://www.mikeash.com/pyblog/friday-qa-2009-05-22-objective-c-class-loading-and-initialization.html