The domain of the orchestration layer shouldn't just be how requests are made to the server, but also how responses are given to a client.
-
-
Replying to @nouswaves
And why should Accept headers be only for content types? The orchestration layer could be a platform for much deeper response structuring.
1 reply 0 retweets 0 likes -
Replying to @nouswaves
Allowing a client to register or use the response formats they want, can be seen as analogous to SQL SELECT statements:
1 reply 0 retweets 0 likes -
Replying to @nouswaves
SELECT c1 AS name, c2 AS birth_date FROM underlying_response;
1 reply 0 retweets 0 likes
A small start here: https://github.com/sebinsua/jstruct … (Very raw idea - perhaps months before I begin to see all of the ways I am wrong.)
10:43 AM - 22 Dec 2013
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.