|
I'm a big fan of JavaScript Object Notation. I treat JSON vs. XML asThe more I've been using JSON, the more I like it. But I'm a self-taught programmer, not a computer scientist, so maybe I just lean more towards the simpler approaches. I hated EJBs because they were so over-designed, and I feel the same way about XML and especially SOAP. Now, if you're in an environment where you need a very strict standardized interface between two entities that otherwise don't talk (a la EDI) then SOAP is probably a reasonable choice. But if you're sending small amounts of program-level data (e.g. data structures) between two machines, then I think JSON is the easiest answer.
internal vs. external views of data. Unless I'm dealing with a product that
already outputs XML (I'm lazy), I always choose JSON over XML for AJAX.
I fall in the same numberless bucket of assuming it performs better with fat
DTDs but I find it much more natural to write JS code that accesses a native
data structure.
Alfred
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.