Re: Flex & RPG

[Aaron Bartell <aaronbartell@xxxxxxxxx>]

If you think about how a parser works it has to check each and every
character to see if it has discovered data, a begin delimiter, and end
delimiter, etc.  The less characters it has to check the better IMO.

Though I would agree that short XML element names help a lot.  On that note,
so does using attributes vs. elements.

Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/


On Thu, Mar 11, 2010 at 1:08 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

> > From: Aaron Bartell
> > I think the key is to NOT use something as verbose as XML...
>
> I've begun to wonder how much of an impact the <tag></tag> delimiters have
> on performance, really.  It's a little more verbose than JSON. But not that
> much.  And you can use short tag names, as an option.
>
> <CUSTID>1234567890</CUSTID>
>
> A Flex application would have no trouble mapping an XML element like that
> to form elements.  I know that Adobe has been promoting a compressed binary
> format for data interchange, which is evidently more streamlined than XML.
>  On the other hand, it seems that you could just use HTTP compression to
> convert XML into compressed binary format to reduce time on the wire
> (transmission time).
>
> -Nathan.
>
>
>
>
> --
> This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
> To post a message email: WEB400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/web400
> or email: WEB400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/web400.