Either I rewrite the back-end code or I write extensions on top of the libraries I am using to attach request metadata to the response.
-
-
-
Replying to @nouswaves
The simpler solution is to reframe requests and responses as explicitly encoded method signatures.
2 replies 0 retweets 0 likes -
-
Replying to @dorkitude
@dorkitude Haha, not my intention. I was writing an extremely chatty front-end to a set of ill-fit APIs.1 reply 0 retweets 0 likes -
Replying to @nouswaves
@dorkitude I found this article this morning which seems relevant: http://thenextweb.com/dd/2013/12/17/future-api-design-orchestration-layer/ …1 reply 0 retweets 0 likes -
Replying to @nouswaves
@dorkitude A lot of complexity in the client for some single-page apps. All due to the need for servers to service multiple clients.1 reply 0 retweets 0 likes -
Replying to @nouswaves
@dorkitude I reckon though that my idea is too extreme: server responses are generic for good reason.1 reply 0 retweets 0 likes -
Replying to @nouswaves
@dorkitude Hard to imagine responses so well-defined they had 1-to-N coupling with all client's response handlers method signatures.1 reply 0 retweets 1 like -
Replying to @nouswaves
@dorkitude Orchestration layers seem like accidental solutions which too often force all of the cost on either the client or the server.1 reply 0 retweets 0 likes
@dorkitude My thoughts are murky: something about the client specifying what they will accept; a man walks towards a door to a building [..]
-
-
Replying to @nouswaves
@dorkitude which has a hole instead of a door handle. The man removes a door handle from his pocket which he screws in. The door opens.0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.