Today I discovered OData. Then I discovered GData. Then I discovered that I don't like either one.
The idea of a data standardization protocol is appealing on the surface, but the two "official" implementations of a common web protocol for data consumption are not my cup of tea. I do like tea, however. But I'm picky about my tea and I'm picky about how I communicate with web servers.
First off, I don't like complicated protocols. I find them annoying as do most other programmers. This is one of the reasons why SOAP slipped on itself and fell on its derriere at the starting gate. /hahagreatjoke
I've been working with JSON a lot lately. It benefits greatly from having native support in every popular scripting language and easy-to-integrate libraries in the few languages that don't. So, if we want to develop a standard protocol, JSON is the starting and ending point for modern development.
For some strange, bizarre reason, when a company builds …
The idea of a data standardization protocol is appealing on the surface, but the two "official" implementations of a common web protocol for data consumption are not my cup of tea. I do like tea, however. But I'm picky about my tea and I'm picky about how I communicate with web servers.
First off, I don't like complicated protocols. I find them annoying as do most other programmers. This is one of the reasons why SOAP slipped on itself and fell on its derriere at the starting gate. /hahagreatjoke
I've been working with JSON a lot lately. It benefits greatly from having native support in every popular scripting language and easy-to-integrate libraries in the few languages that don't. So, if we want to develop a standard protocol, JSON is the starting and ending point for modern development.
For some strange, bizarre reason, when a company builds …