Re: AJAX without XML
- From: "Dag Sunde" <me@xxxxxxxxxxxx>
- Date: Sat, 26 Nov 2005 19:44:29 GMT
"Thomas 'PointedEars' Lahn" <PointedEars@xxxxxx> wrote in message
news:16193602.pLa2S67eGz@xxxxxxxxxxxxxxxxx
> dave.c.johnson@xxxxxxxxx wrote:
>
>> Using JavaScript as the data transport encoding [...]
>
> I beg your pardon? The transport/transfer _encoding_ never was
> JavaScript,
> but was and is US-ASCII, ISO-8859-XX or UTF-16, for example. Perhaps you
> meant "data _format_" which is a completely different thing.
>
>> But if you are returning an array of data that needs to get into the
>> web page DOM (and will maybe need sorting / filtering on the client)
>> then use XML since XSL can be much easier to use for some people and it
>> can be re-used on both the client and server.
>
> What are you talking about? An array is a data structure. If that is
> returned, JSON is definitely the best format as the language it is built
> on has built-in array support. Perhaps you meant returning a DOM subtree
> with several child elements where XML would be more appropriate.
In some cases, it can be preferable to just return a string with
semicolon separated values, and .split() it on arrival. If nothing
else, it is compact, and does not depend on any libraries being present.
--
Dag.
.
- Prev by Date: white papers concerning call centre queuing..
- Next by Date: Re: white papers concerning call centre queuing..
- Previous by thread: white papers concerning call centre queuing..
- Next by thread: OOAD Study Guide
- Index(es):
Relevant Pages
|
