Remove deprecated line from podspec
Bugfix: Add preprocessor definition to podspec

Otherwise the library version constant is missing when including libPusher via a Podfile
Bugfix, now uses correct pongTimeout
Invalidate timers on disconnect

Otherwise library tries to send a ping after disconnect, causing assertion to fail
Remove unnecessary pusher:ping event handling

This will never be sent by the server since the WebSocket draft in use supports native pings
Reset the pong timer on any activity

This simplifies the timer logic: It's no longer possible to have to a ping & a pong timer active at the same time.

Also consistent with the js client behaviour
Merge pull request #118 from mloughran/client_activity_timeout_fixes

Client activity timeout fixes
Ignore xccheckout files
Update to the latest version of CocoaPods and update Xcode project
files.
Inhibit CocoaPods warnings.
Mock connection must call the designated initialiser or it will not have
appropriate default ping/pong timeout values.
Deprecated the use of auto-connect and any methods that take a 
connectAutomatically parameter.

This behaviour was generally undesirable as you wouldn't normally
want to connect without setting a delegate first, which resulted
in extra factory methods that take the delegate or having to pass
NO and then set the delegate. It was generally confusing.

It's simpler to have just two factory methods; one with an optional
encrypted parameter, and let the user call connect when they are ready.

The deprecated methods will continue to call connect automatically if
requested but this will go away in 1.6.
Add missing deprecated delegate call

(removed by 6b5989b0)
Should reconnect after delay for unknown errors

Otherwise libPusher will not reconnect automatically after a whole range of errors
Log deprecation notices when calling deprecated delegate methods.

This is because deprecated delegate method usage will not be detected
by the compiler because clients do not call delegate methods, they
just define them.

Closes #120.
Refactor presence channel membership handling, taking a similar
approach to the JavaScript client.
Add some specs around presence channel subscription and member handling.
It is permissible to call unsubscribe on a channel that may have been
marked as not subscribed (e.g. due to a disconnection).

This is because an explicit unsubscribe marks the end of the lifecycle
of that channel object: all bindings are removed and internal references
to that object are discarded.

I've added a comment that elaborates on this.
Renamed to handleDisconnect: as it signals the intent more clearly 
without leaking implementation details of *what* channels do on 
disconnect (i.e. they become implicitly unsubscribed).
Expose the URL of a connection as a read-only property.