-- Original message --
programmatically I find json soooo much easier, rather than having to parse a file you're referring to object elements. makes xml redundant as far as I'm concerned.
On 26 September 2011 22:26, Timothy Green <tim...@green.name> wrote:
Well, I wasn't planning on using namespaces! <headhurts>
TRiG.
On 26 September 2011 22:14, Steve Dunkley <steve....@gmail.com> wrote:
> json is a *LOT* simpler than xml ;¬)
>
> On 26 September 2011 22:12, Timothy Green <tim...@green.name> wrote:
>>
>> > If h2g2 has a smartphone app, that app is going to need to ask questions
>>
>> And not just a smartphone app. If you have an Ajaxy skin, it'll need
>> an API too. Ajax (asynchronous javascript and XML, though it's not
>> necessarly asynchronous and not necessarily XML), basically means
>> sending information between the browser and the server in the
>> background. So when you click somewhere, or press a button, the
>> javascript tells your browser that, instead of doing what it normally
>> would when you click here or press that button, it should instead send
>> information in the background to the server (using the API), await the
>> server response (using the API), and react accordingly. This would
>> mean that the browsing experience can be smoother. Facebook uses a lot
>> of Ajax, so when you submit a comment it doesn't reload the entire
>> pƥ