Open lukeredpath opened 8 years ago
First point seems like a great idea and at first glance, it doesn't look like there's a massive amount more work to be done for it. Links nicely with the second one in that removing (or abstracting) the baked-in auth that uses NSURLConnection can be part of the same work that involves moving over to using NSURLSession instead.
As I mentioned before, I also agree that splitting up the library into a Websocket library and an HTTP library is a good idea.
I'm also definitely game for a re-write in Swift. I threw together a Swift library (here)[https://github.com/pusher-community/pusher-websocket-swift] but am happy for a libPusher written in Swift to become the de facto library for all Apple software integrations (iOS, OSX, tvOS maybe even watchOS, and whether Objective-C or Swift is being used).
And a move over to the Pusher org would be great :+1:
@hamchapman revisiting this, I'd like to push for one last release (1.7) before focussing on 2.0 and a Swift rewrite.
Sounds good to me!
Some thoughts about the direction of libPusher for version 2:
Anything else @hamchapman?