Badly formatted xml, damn.
Here's their example 1 oh yeah works fine in JSON but what if I want xml 2? That's not valid xml, so my xml parser isn't picking it up. Can't have a node starting with a number like that. Why put the value in as one of the node names like that anyway? Wonder if I've done this in my own api work at all? Maybe, to give the option of returning multiple values... Ah good bit.ly/roRyu 3, and neither should you bit.ly 4.
Our new highchair 5 has been dispatched!
Node: Javascript (programming language of the internets) on the server side.
⬅️ @pauly http://bit.ly/1ovrX5#m13021 ignore me they have one here http://bit.ly/3OPjxk :: My name's Gerald, funnily enough, and I'd like to push a bit of advertising your way ➡️
Paul Clarkeʼs weblog - I live in Hythe near Folkestone, Kent. Wed and dad to two, I am a full stack web engineer, and I do mostly js / nodejs, some ruby, other languages etc. I like pubs, parkrun, eating, home-automation + other diy jiggery-pokery, history, tree stuff, Television, squirrels, pirates, lego, + time travel.