DCTConnectionController and the associated classes are my way to handle URL connections, specifically those made to RESTful services.
Connection controller subclasses should manage the connection and handle callbacks, most likely translating them into model objects that make sense to the rest of the application. In this way connection controllers can be called by other objects without needing any knowledge of how the connection is performed or the web API calls that are needed.
DCTConnectionQueue is used to queue up connection controllers, and managed the order in which they are run. It also allows the limiting of the amount of connections occurring.
DCTConnectionGroup is class to monitor a group of connection controllers and be notified when they have all ended; Be it through successfully finishing, failure or cancellation.
There is a category on
DCTConnectionQueue to allow access to a global queue, and a convenience method on DCTConnectionController to easily queue connections on this global queue. You are, however, not bound to using this global queue and can use multiple queues as you wish.
DCTConnectionController 2.1 Notes
DCTConnectionGroupclass to monitor a group of connections controllers.
-[DCTConnectionQueue addConnectionGroup:]to queue up a connection group.
- Adds a notification that the connection controller needs display (through a webview) to allow a view layer to handle things like OAuth connections.
-[DCTConnectionController returnedObject]is now of type
- Moves the
DCTConnectionControllerto a category, as well as the delegate handling.
- Makes the
downloadPathproperty setable, moving it to a category. Setting this will copy the downloaded data to the path provided. Warning: You can no long override this in a subclass to achieve this, it must be set.
- Fixes a bug where the same connection controller would get queued up more than once if
-[DCTConnectionQueue addConnectionController:]was called more than once.
- Fixes a bug where called
-[DCTConnectionQueue addConnectionController:]would not check for duplicates on the queue.
-[DCTConnectionControllerDelegate connectionController:didReceiveObject:], use
-[DCTConnectionControllerDelegate connectionControllerDidFinish:]instead. The original delegate method is still called in version 2.1 though.
DCTConnectionController 2.0 Notes
- The API for the new version of
DCTConnectionControllerhas been revised and care should be handled when upgrading to the new version.
- The functionality of
DCTRequestConnectionControllerhave been moved into
- The multitasking additions to
DCTConnectionQueuehave been moved to their own repository to be further built upon.
- Handling of the iOS activity indicator has been moved to DCTNetworkActivityIndicatorController. To get the indicator functionality of DCTConnectionController 1.0, add
DCTNetworkActivityIndicatorControllerand it will automatically register for notifications sent by
The UIKit category on
DCTConnectionQueue allows it to handle iOS multitasking and the application-wide network activity indicator. As of DCTConnectionController 2.0, this category is now in its own repository.
Currently, the following services have been written using connection controllers:
There is a new branch structure for DCTConnectionController 2.0, master and demo. Unlike previous versions, master is now the branch to use as a submodule.
The master branch contains the code and should be used if you want to add these extensions as a git submodule in other projects. It will only contain the class files themselves without the Xcode project or example classes. This is preferable as it will keep your directories clean of any code which is unnecessary to your working project.
To add this project as a submodule you should run the following from inside your project’s git repository:
git submodule add git://github.com/danielctull/DCTConnectionController.git
To keep up to date with the latest changes `cd` into the directory that contains this submodule and pull the newest changes as usual:
git pull origin
This contains an Xcode project that demonstrates the code and is the branch to use to see how to use the code. The demo branch contains a submodule reference to the master branch to bring in the library classes.
To clone the demo branch, while also pulling in any necessary submodules run the following command:
git clone -b demo --recursive git://github.com/danielctull/DCTConnectionController.git
When changing to the demo branch you will need to run through the following set of commands:
git checkout demo git submodule init git submodule update
After these you will see the example project and the library code will be in a sub-directory.
Sometimes, there may be artefacts left over when switching from demo to master. These are files that are ignored by git and are easily cleaned up by running
git clean -dxf
Examples of some of these features can be found in the iPhone app delegate.
Copyright © 2010 Daniel Tull. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- Neither the name of the author nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.