Advanced

Ajax tradeoffs and the right XML encoding for you

Posted by solrac on · Post a comment
IBM/developerWorks; By Dethe Elza and David Mertz, Ph.D
Mail this story
Print this story

This article gives you everything you need to decide which is the right way to encode your data for your Ajax application.

When using XML in your Ajax apps you have to ask yourself what flavor of XML fits your needs best. Several tradeoffs are involved. Some of the obvious choices to pick from are (X)HTML, SVG or X3D if your data is graphical, Atom for snippets of data over time, OPML for simple outlines, and RDF for semantic graphs. This article gives you everything you need to decide which is the right way to encode your data for your Ajax application.

Full Story

  Nav
» Read more about: Groups: IBM; Story Type: News Story

» Get new stories by e-mail: nightly or as they are published

« Return to the newswire homepage

  Related stories
» More like this

Comments

No comments yet. Be the first.

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post