On Sep 25, 2018, at 12:13, Yitzhak B. Solórzano <[email protected]> wrote:
> I find that XML software parsing process can take a long
> time. One reason for this problem is the DOM manipulation libraries
> that require more memory to handle large XML files. JSON uses less
> data overall, so you reduce the cost and increase the parsing speed;
> JSON structure is straightforward and readable. You have an easier
> time mapping to domain objects, no matter what programming language
> you're working with,
>
> Just compare two structures, and find what's more easy and eficient.
No arguments there.
If we were starting the development of the remote API today, it’s quite
possible that JSON would have been the protocol selected. However, the existing
XML-based setup has been part of Rivendell for years, is a publicly declared
and stable API, and is relied upon by multiple third-party client applications.
It’s not going away. To justify adding a *second* remote API alongside would
require that that new setup offer significant —indeed, dramatic — improvements
in functionality over the existing one. I just don’t see the relatively modest
performance increases of a JSON implementation as justifying the required
development and maintenance resources needed to make it happen.
Cheers!
|----------------------------------------------------------------------|
| Frederick F. Gleason, Jr. | Chief Developer |
| | Paravel Systems |
|----------------------------------------------------------------------|
| Like the ski resort of girls looking for husbands and husbands |
| looking for girls, the situation is not as symmetrical as it might |
| seem. |
| -- Alan McKay |
|----------------------------------------------------------------------|
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
