Using Node.js as an access point for mobile application API -


i'm not sure if i've quite grokked node.js yet, want implement it, cause understand pretty friggen sweet.

i've got mobile application uses api third party. users typically open see if new. occurred me long respect third party api's polling limits (and other restrictions) simulate push based system , allow user notified once new.

basically implement api polling node.js server on sort of interval, , make mobile app point node.js server instead of end point api.

i figure number of reasons:

  • takes load off phone's data usage (since can cache things on both phone , server). huge win users have pay-per-byte data plan
  • allows central location storing / accessing data
  • lets me optimization on server side (if 2 users happen subscribe same feed can in 1 request.

i figure bad number of reasons:

  • if my server goes down, apps die. acting go-between node.js implementation may introduce higher number of fail points.
  • when third party releases additions api, requires me implement changes in 2 places, instead of one.

my question this: in general, practice? if not, why?

your proxy idea fine, in it:

  1. converts poll push
  2. insulates client api changes
  3. allows optimizations

i feel #1 important.


Comments

Popular posts from this blog

jquery - Invalid Assignment Left-Hand Side -

java - Play! framework 2.0: How to display multiple image? -

gmail - Is there any documentation for read-only access to the Google Contacts API? -