fivesquaresoftware/cumulus

Cumulus is a simple, powerful and blazing fast Cocoa HTTP+REST client that makes creating Cloud-backed apps stupidly easy.

cumulus's Issues

Expose control of the request delegate queue on CMResource so that request delegate callbacks can use something other than the main run loop

Allow users of CMResource to:

• Pause and resume dispatch of requests
• Control how many concurrent requests are allowed at any one time

Activity spinner not working on iOS

Server file system based specs fail when running on devices

Lots of tests that reference files that are in the server directory for comparison purposes fail when running on device. Figure out how to get these working.

Drop support for iOS 5

Allow for setting max concurrent requests on a resource and on static interface

This should be a per-resource setting and include some simple optimal defaults.

Add the ability to chain response post processors

Currently a request only takes a single post processing block. Allow multiple blocks to be chained and receive the output of the previous block.

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.

Allow for chunked downloads

Change the interface of resource group to take a work block instead of requiring manually adding of resources

Mac Spec Runner

Currently there is no spec runner for Mac OS, create one.

External benchmarks

Create an app in examples that runs a set of benchmarks against an external service

Allow for request groups to cancel all their requests

CMResourceContext should have some way to cancel the requests launched for a particular work block

Expose request delegate queue in request and resource

Can be useful if you have some esoteric control needs

Calculate optimal max concurrent requests base don actual performance

Currently optimal max requests is calculated in CMRequestQueue using some simple math based on platform and number of cores. It would be better to calculate this dynamically and include real time performance metrics in the equation.

Update programming guide with new information

Replace most of the query based resource request signatures with a persistent query object

Seems like for DELETE, POST & PUT 99% of the time no one is going to use the query interfaces. The main reason it's needed at all is just to support non-conforming services that use a query string to pass things that should be in the headers (keys, versions, etc).

Keep the query for gets and heads, but add a persistent query object as a resource attribute that gets tacked on to all requests to server the other purpose.

Convert locks around CMResource _requestsInternal to use barrier blocks rather than semaphores

This is primarily an optimization to allow concurrent reads

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.

Make RCResource <NSCoding>

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

Canceling a chunked download request only cancels running chunks (not waiting chunks)

Make downloads resumable

Allow downloads to be resumed

Make RCResource be <NSCopying>

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

iOS 9.0 warning issues

In CMFormCoder.m at line 126 Xcode is showing a warning related to
CFURLCreateStringByAddingPercentEscapes' is deprecated: first deprecated in iOS 9.0.
CFBridgingRelease(CFURLCreateStringByAddingPercentEscapes(NULL, (CFStringRef)inputString, NULL, (CFStringRef)charsToEncode, CFStringConvertNSStringEncodingToEncoding(encoding)));

Also In CMFormCoder.m at line 141 Xcode is showing a warning related to
CFURLCreateStringByReplacingPercentEscapesUsingEncoding' is deprecated: first deprecated in iOS
9.0.
NSString *decodedString = (__bridge_transfer NSString *)CFURLCreateStringByReplacingPercentEscapesUsingEncoding(NULL, (CFStringRef)inputString, CFSTR(""), CFStringConvertNSStringEncodingToEncoding(encoding));

Child resources not appending parent query to requests

Group requests from resource context occasionally crash

Crashes realtes to inserting nil object occasionally when a request leaves a group with a response. All the objects look valid, tough to say what's going on.

need to encode query.

near line 770:

//NSString *requestQueryString = [requestQuery toQueryString];
NSString *requestQueryString = [[requestQuery toQueryString]stringByAddingPercentEscapesUsingEncoding:NSUTF8StringEncoding];

Add a way to enable logging in release builds

Currently logging is always off unless DEBUG is true. Allow a flag to be set that enables logging even when DEBUG is undef or NO.

$_POST is empy

I have a php server. When I do [self.someResource post:serializedQueryString withCompletionBlock:nil]; nothing happens to appear in $_POST array. How dow I fix it?

Add last modified to resource to set If-Modified-Since header

Setting a data automatically sets If-Modified-Since header. Add a property to allow the resource to automatically track this based on the response headers as well.

CMResource queryString is returning nil when a query is set

Add the ability to fetch relationships along with a request for the receiving resource