-
Notifications
You must be signed in to change notification settings - Fork 266
AFNetworking 2.0 support #28
Comments
I've been thinking about this myself. @ryanfitz already sent a great pull request integrating AFNetworking to 2.0. But some projects still use AFNetworking 1.3.0, and particularly, for those using RestKit (like me), it hasn't yet moved to AFNetworking to 2.0 either. Would it be a way to support both? 1.3 and 2.0? |
Honestly i haven't tried it , the migration process from 1.3 to 2.0 is really easy to do , however if your app requires 1.3 there is a problem . My app requires 2.0 and i have a problem with this library, should i try using ryan's pull ? |
I'll suggest to give a try to Ryan's pull. The only issue is that you would not be able to install it with pods... |
I'll give it a go , thanks . Why don't you make a version available that uses afn 2.0 . Right now you can pod AFN 1.3 and 2.0 , similarly a user could pod DZN 1.0 and let's say 2.0 ( which uses AFN 2.0 ) . Wouldn't this solve the issue? |
It's actually a good idea, but the library still need hot fixes to move to 2.0 |
Theoretically if ryan's pull solves the issue and migrates it to 2.0 , just create 2.0 and update it using that ? |
Actually my question was more related to git. |
The changes would only apply to the branch you were On Tuesday, March 18, 2014, Ignacio Romero Z. notifications@github.com
|
That's what I though. I'm going to read a bit more about this and get back to you for a solution. |
Closing this for now. |
How can i integrate this in a project that is already using AFNetworking 2.0 , one of your classes is using AFHTTPClient which is no longer available in 2.0 ?
The text was updated successfully, but these errors were encountered: