Unsubscribed channels are not released about libpusher

[lukeredpath]

Hi Tim. I'll take a look into this. FWIW, if you compile the ARC version of the library as a static library (there are precompiled downloads available) you can use it in your non ARC project without any problems.

[tim17x6]

I tried to destroy unsubscribed channels by removing them from the 'channels' dictionary in the PTPusher class. This did not seem to work since the PTPusher 'dispatcher' object still held a reference to all channels. This reference was established when each channel was bound to the 'pusher_internal:subscription_succeeded' and 'subscription_error' events. Since these events are never unbound, channel objects are never released - event after they are unsubscribed.

I would like to be able to subscribed and unsubscribe from channels, and then clear the unsubscribed channels from memory. In order to do this, it seems that channels need to be able to cleanly unbind from all internal and external events. It seems that this would be pretty standard functionality for most apps that use push messaging.

Please let me know if I am thinking about this incorrectly or doing something wrong. I would be grateful for any guidance.

Thanks,
Tim

[tim17x6]

I think I found a bug related to this issue. In PTPusherChannel.m method initWithName:pusher:

These lines:
[pusher bindToEventNamed:@"pusher_internal:subscription_succeeded"
target:self action:@selector(handleSubscribeEvent:)];
[pusher bindToEventNamed:@"subscription_error"
target:self action:@selector(handleSubscribeErrorEvent:)];

Should be.
[self bindToEventNamed:@"pusher_internal:subscription_succeeded"
target:self action:@selector(handleSubscribeEvent:)];
[self bindToEventNamed:@"subscription_error"
target:self action:@selector(handleSubscribeErrorEvent:)];

This fixes some problems with reconnecting to multiple channels on reconnection.

[lukeredpath]

@tim17x6 could you please try the use-socketrocket-backend branch and see if this fixes the problem for you?

[lukeredpath]

This should be fixed in 1.2, which I released today.