JavaScript is required to use Bungie.net

Forums

originally posted in:BungieNetPlatform
originally posted in: Manifest -> Schema -> SQL
4/29/2015 8:36:08 AM
3
I was actually exploring a similar effort as yours but instead of using SQL I opted to use the CouchDB database instead. There are a couple of reason why I went with couchdb instead: - CouchDB is already JSON based so there is no need to generate schema's. - CouchDB supports an HTTP/JSON API which makes integration with mobile & browser based applications a lot easier. - With the build-in document versioning you can see what changes are made between different manifest updates. So when you load in a new manifest update you can easily sync this between various of consumers. See next point. - The replication protocol is super powerful and allows you to completely sync the db to a mobile device for offline use for example. - Not relational, as we have no control over the data structure provided in the manifest this will be easier to maintain as there is no need massive schema changes. - Easy to administer and backup. So far, I haven't encountered any issues with this attempt. But would love to read your blog post about your experiences once you're done :)
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • do you have an example on how to achieve this ? or somewhere we can use your work ? that sounds like an amazing idea, and i will need to do this at some point so that i can update the content of my app without having to push for an update trough the store.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Yup, that was also one of my use-cases for my apps. The beauty of this approach is that once the manifest is changed and updated in the database only the diff will be retrieved by your application. So there's no need for data parsing and transformation in the app or publishing a new version just because the data changed. As for the work it self. What i've build is a really rough proof of concept that is in no way stable yet. But i'm a big Open Source enthousiast (currently maintaining hundreds of populair Node.js modules) so once my application running somewhat stable I will release - The mobile application. - The database transformation scripts - The actual database setup scripts which will most likely result in to a Docker container for easy deployment - A public URL of the CouchDB server so others can just hook up a replicator process to it and get updates - New JavaScript (ReactNative) Destiny API library - And tons of misc modules which render various of components my app But i'll announce this all in a new topic once it's done which should hopefully be in a week or two depending on how fast I can get the oAuth flows to work with a WebView in iOS. But I can see if I can open source the database work I've been doing a bit sooner on GitHub.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • Nice man, thank you. If you need help with the auth in Android i can give you my login code, but in IOS i don't know anything, so i can't help you there :)

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon