search

troystump / LoLAPI

RESTful Objective-C client for the popular online game "League of Legends" by Riot Games.
Apache License 2.0
10 stars 3 forks source link

Offline? #7

Open csmoon2 opened 9 years ago

csmoon2 commented 9 years ago

Just a question of whether if I can save the json input and run the api with that json in an offline environment? Didn't go through all the code yet but I am assuming you get a huge chunk of json data and parse it in different classes? Would it be possible to save that input and parse the saved input when the user is offline? If not, should I be looking at CoreData/NSUserDefaults in saving the necessary data separately?

Thanks for your work in this project!

troystump commented 9 years ago

Hey there, thanks for your question!

Definitely the next thing coming from this API is saving off the webservice response(s) as managed objects in CoreData.

I'm actually going to spend some time this weekend and see how far I can get with implementing CoreData layer. Hopefully all goes well!

For now, you could probably store the objects initially and then call any web service depending on conditions you have set in your app. It's a bit of a workaround until I get the CoreData layer on, but I feel it would work.

csmoon2 commented 9 years ago

Oh great! I'll look forward to seeing it in the future. Thanks!

troystump commented 9 years ago

Thanks for following this Library and helping me to make it the best!

As a recent update, I have the Core Data stack working successfully for Riot's Status API. Now it's just a matter of rinse and repeat for all the other APIs. New release should be coming soon with Core Data object graphs (1 per api) and store persistency via a single, centralized sqllite db.

csmoon2 commented 9 years ago

Thanks so much for the work you put into this project. And thanks for the update on the offline function. I hope you have a wonderful Thanksgiving!~

csmoon2 commented 9 years ago

Any ETAs on the new API?

troystump commented 9 years ago

Hey! Sorry I have been quiet.. I was working on solving a complicated issue of transforming Dictionary's from a few of the APIs to NSSets and making sure relationships were setup correctly to fetch from Core Data was working correctly.

All in all, its taking some time because I have also added the missing Match and MatchHistory APIs to the library. I have 3 APIs left to add support for Core Data, and they are probably the easiest ones. This weekend I hope to see about getting a new release out for you play with.

Thanks for checking in!

jstock78 commented 9 years ago

Hey Troy, any chance you can add the Match and MatchHistory APIs? I was planning on working on implementing them next week if not.