blob: 120cd849a80b638746761253b4c00de6f7bb43ec [file] [log] [blame]
"name": "OperationsRunner",
"platforms": {
"ios": "7.0"
"version": "3.1.2",
"license": {
"type": "BSD"
"homepage": "",
"authors": {
"David Hoerl": ""
"summary": "Lightweight Framework For using NSURLSession",
"source": {
"git": "",
"tag": "3.1.2"
"source_files": "WhatYouNeediOS7+/[OW]*.{h,m}",
"requires_arc": true,
"preserve_paths": [
"description": "OperationsRunner makes adding network fetchers to a controlling class simple and painless.\n\nOperationsRunner.h enumerates the handful of steps required. Once added, you instantiate subclasses of the WebFetcher class, configure them, then schedule then to run. Fetchers message one sific method in your control class, returning either the requested data (or response for a POST), or a failure indication.\n \nReasons to use this project:\n- Empower any class you want to perform asynchronous HTTP activity easily and quickly.\n- Lightweight - only a few hundred lines of code. Enable the log messages to see EXACTLY what is happening.\n- With one message, you can essentially tear down all current sessions and activity (e.g., user hit the Back button).\n- Use a hierarchy of WebFetcher subclasses to add increasing complexity. The fetchers can perform processing functions, e.g. resize images, in the same background queue used by the fetcher.\n- Do you really want to use some huge bloated framework, where you have no control or even understanding.\n- Look at URfetcher7 and URSessionDelegate for an example of how to specialize (subclass) WebFetcher and ORSessionDelegate restively.\n\n"