Security comes not just by only enabling HTTPS, and using Identity
Provider (IdP),
which issues access tokens, no need to explain that XML is much more
difficult to parse than JSON, and JSON is parsed into a ready-to-use
JavaScript object...
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.
XML
<car>
<company>Volkswagen</company>
<name>Vento</name>
<price>800000</price>
</car>
JSON
{
"company": Volkswagen,
"name": "Vento",
"price": 800000
{
El mar., 25 de sep. de 2018 a la(s) 12:38, Fred Gleason
([email protected]) escribió:
>
> On Sep 24, 2018, at 20:56, Yitzhak B. Solórzano <[email protected]> wrote:
>
> Advantages is plenty of, like security (Because you can use top
> security on it),
>
>
> SSL is not ‘top security’?
>
>
> easy implementation (anyone who understand basic of
> JSON could do an app 100% compatible), easy to understand (JSON
> speaks) and flexibility (can be use on web app, mobile apps, tablet
> apps)…
>
>
> If you happen to be using a client platform where JSON is the native and
> preferred transfer format, sure. The same argument could be made for XML,
> LDAP, etc, etc. “JSON for the sake of JSON” is a non-starter however.
>
>
> I work for a software company who develops for more
> sophisticated software and that’s where my idea comes from, you’ll
> have speed, you can access from everywhere because it uses a very
> light HTTP data transfer.
>
>
> Yes, a speed optimization, agreed. I’m not convinced that that alone would
> justify the development resources needed to make it happen though. Unless
> you’re volunteering? :)
>
> Cheers!
>
>
> |----------------------------------------------------------------------|
> | Frederick F. Gleason, Jr. | Chief Developer |
> | | Paravel Systems |
> |----------------------------------------------------------------------|
> | When in doubt, use brute force. |
> | -- Ken Thompson |
> |----------------------------------------------------------------------|
>
> _______________________________________________
> Rivendell-dev mailing list
> [email protected]
> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
--
(Isaac)
Yitzhak B. Solórzano.
יִצְחַק בטנקור
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
