Hi, As a javascript developer it does feel like a natural fit to use JSON instead of XML. The performance gains will probably be minimal, but IMO both server side and client side code should become simpler as JSON provides data structures like strings, numbers, booleans, arrays, dictionaries and null, where XML is just a collection of string values that get a strong-typed meaning once some code parses/creates it, adding an extra level of complexity both on the server and on the client.
-- Kind regards, Met vriendelijke groet, Arthur Bogaart Hippo [email protected] 2012/1/9 tetsuo <[email protected]> > I don't think JSON would bring any benefit, and it could cause a > number of security issues. > > > http://directwebremoting.org/blog/joe/2007/03/05/json_is_not_as_safe_as_people_think_it_is.html > > > > > On Mon, Jan 9, 2012 at 12:22 PM, Martin Grigorov <[email protected]> > wrote: > > Hi, > > > > Are we interested in reworking AjaxRequestTarget to produce JSON > > response instead of XML ? > > Do you see any advantages in this except a bit shorter response ? > > > > Currently wicket-ajax.js uses DOMParser to create the XML document in > > 1.5 and jQuery creates the document for us in 6.0. > > I'm not sure whether there is any performance benefit in JSON parsing > > at the client side... > > > > -- > > Martin Grigorov > > jWeekend > > Training, Consulting, Development > > http://jWeekend.com >
