Forum Moderators: coopster
In defense of that statement though, I would propose that delving into something such as JSON would likely mean you have a project that requires such an undertaking. Looks to me like folks are still shaking the whole "XMLHTTPRequest/XML/AJAX/JSON" model around. Which is the best method? And why? Do I actually need to use this technology, does my project require it?
It seems to be a hot topic lately and many conferences have some form of discussion going on around it as do web seminars, etc. I took one in myself recently and was impressed with capabilities ... but who/why/where/what/when do I have applicational use? And at that time, which methodology would I embrace?
"No" answer here either, sorry ;)
For many jobs, JSON will be simpler to implement. But both JSON and XML will have their place.
[edited by: coopster at 12:54 pm (utc) on Sep. 8, 2006]
[edit reason] no urls please TOS [webmasterworld.com] [/edit]