?

Log in

So today at work I ended up explaining to a colleague that… - 'Twas brillig, and the slithy toves did gyre and gimble in the wabe [entries|archive|friends|userinfo]
Thomas

[ website | Beware the Jabberwock... ]
[ deviantArt | the-boggyb ]
[ FanFiction | Torkell ]
[ Tumblr | torkellr ]

Links
[Random links| BBC news | Vulture Central | Slashdot | Dangerous Prototypes | LWN | Raspberry Pi]
[Fellow blogs| a Half Empty Glass | the Broken Cube | The Music Jungle | Please remove your feet | A letter from home]
[Other haunts| Un4seen Developments | Jazz 2 Online | EmuTalk.net | Feng's shui]

[Wednesday 4th November 2015 at 10:57 pm]
Thomas

boggyb
[Tags|]

So today at work I ended up explaining to a colleague that XMLHttpRequest isn't just for JSON, but that it can parse XML documents and turn them into a nice object structure. He was thinking that I'd have to receive the XML as text and use some XML-to-JS library to parse it (which to be fair I may still have to do - some of the code I'm writing will run server-side where XMLHttpRequest doesn't exist).

For those who don't know their web development history, the original point of XMLHttpRequest was to let JavaScript make XML requests and handle XML responses. Using it for JSON came much later.
Link | Previous Entry | Share | Next Entry[ One penny | Penny for your thoughts? ]

Comments:
[User Picture]From: crschmidt
Thursday 5th November 2015 at 2:50 am (UTC)
I assume that he wasn't actually using XMLHttpRequest directly, but some wrapper that made it less obvious what it was for?
(Reply) (Thread)