Ensured parameters order on equality assertion is consistent. Correct order is actual, expected, message.
Refactor the ORRESTCall so that:
- call is not started at initialisation, -start method must explicitly be used
- NSURLConnection is guaranteed to run on the main thread, ensuring there's always a runloop to handle connection appropriately, even if ORRESTCall is started from background thread
Now that client library ensures REST calls are scheduled on the main thread, revert cache to ensure loading is done in the background