comment on

Greetings GoCool,

Just my own personal opinion (and it seems to work out well for me in my particular situation) is: Why translate a data structure from Perl to XML and then from XML to JavaScript data object if all you're ever going to do with AJAX is talk between Perl and JavaScript? Seems faster, simpler, and easier to just go direct from Perl to JavaScript, which is why I like JSON so much.

I'm not against XML, but I am against having to use XML when there's really no reason to do so. If I were going to de-link my data provider (Perl CGI/mod_perl) from my GUI (JavaScript) so that some developer who's not me could build a hook into the data source and build their own GUI, then XML would make a lot of sense. However, if I don't really care about exposing my data source, then I don't want to waste the time with XML.

Just my opinion. There's more than one way to do it.

gryphon
Whitepages.com Development Manager (DSMS)
code('Perl') || die;

In reply to Re^2: copying perl array to javascript array by gryphon
in thread copying perl array to javascript array by Rainmaker

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl-Sensitive Sunglasses
	PerlMonks