- From: Paul Denning <pauld@m...>
- To: "G. Ken Holman" <gkholman@C...>, Mukul Gandhi<gandhi.mukul@g...>, "xml-dev@l..." <xml-dev@l...>
- Date: Tue, 1 Aug 2017 11:14:17 -0400
Agree JSON is fit for purpose where the coupling is tight, i.e., the
_javascript_ running on the browser is typically sent from the
server. The server code and the _javascript_ sent to the browser are
managed as a tightly coupled pair. If the server needs to change,
the _javascript_ (sent from the server to be run on the client side)
is updated at the same time. The independent evolution (loose
coupling) of the client and the server is not really an issue in
this case.
Using JSON may not be optimal for true machine-to-machine exchanges
where each side needs to evolve independently (yet both side are
dependent on a good specification of the exchange).
Paul
On 2017-08-01 10:12 AM, G. Ken Holman
wrote:
And I posit that JSON is fit for purpose only for quickly
populating browser memory structures for _javascript_ manipulation
in a tight coupling between sender and receiver. I claim
it is not fit for purpose as a generalized information
serialization format where decoupling between sender and receiver
is paramount.
|
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
|
Cart
