-
Notifications
You must be signed in to change notification settings - Fork 0
Home
##TOC (WIP)
- What is JsonR ?
- Who is it intended for ?
- Why no just use library X or Y ?
- How can i participate ?
- Implementation Spec: Client-Side
- Implementation Spec: Server-Side
##What is JsonR ? // ... WIP
##Who is it intended for ? While anyone can use it, doesn't mean that everyone should. If your website is Ajax intensive and you are serving tens to hundreds of visitors/day, then it's probably not for you. If you are serving hundreds to thousands, then it's maybe something to take into consideration. However if you are serving tens of thousands and up, then this is definitely something you should look into.
Not only are websites becoming more and more Ajax intensive to deliver a better and more fluid user experience all the time, but mobile websites & web-services have never been as widespread as today. Take any mobile application out there and what do you have ? A GUI that's installed onto the device, and then just pure web-service goodness to get the data to the client! Single Page Applications fall into the same category. Facebook, Twitter, Google+ are all SPA's or at least hybrid SPA's
What this means is that around 80% of your traffic is downstream, and probably 90% of that downstream data is dealing with collections (user lists, contact lists, conversation lists, etc...)
Not to mention the trend of everyone getting into cloud based services & hosting where you pay a slight premium for the flexibility this offers you, but where you pay by the CPU cycle, number of requests, and GB's in/out.
In those scenarios JsonR will help you by:
- Cutting your bandwidth costs
- Less data, means faster transmission, which in return means your client waits less to get your data
- Which again means less waiting & happier clients.
##Why no just use library X or Y ? While roaming around trying to find 3rd party library support from different serializer vendors I've repeatedly heard the same things over and over:
#####Why not use JsonH ? // ... WIP
#####Why not use MsgPack ? // ... WIP
#####Why not use Protobuf ? // ... WIP
#####Why not use RJson ? // ... WIP
#####Why not use JSV ? // ... WIP
#####This will just add extra bloat for something that will be rarely used // ... WIP
#####It's not standard and you need client side support // ... WIP
##How can i participate ? ####If you build a client or server-side implementation that supports the JsonR Spec, please submit it to the project. ####Please do so even if an implementation in your language already exists, but you think your version adds a nice twist (usage, performance, api style, etc)
- Clone the project
- Add your implementation
- Issue a pull request
- Smile !
##Implementation Spec: Client-Side // ... WIP
##Implementation Spec: Server-Side // ... WIP