1/ wow, the Ruby Hash.from_xml() sucks feed it "<Foo>text</Foo>" and it gives { Foo => text } feed it <Foo a=b/> and it gives { Foo => { a => b } } Both good results. But combine those two XML features ...
-
-
4/ The problem I'm trying to solve by parsing XML is parsing XML. Not trying to be (too) snarky, but I am coding to a Very Baroque web interface by a Very Baroque Large Firm, and their web services speaks XML. >>> https://twitter.com/RedeemedCat/status/1283074012638179328 …
This Tweet is unavailable.Show this thread -
5/ and I've already got my server which handles inbound SOAP / XML requests from LARGE FIRM working, and I'm composing XML responses, as I am required to so now in my mock / test harness / regression test client which pretends to be BIG FIRM I'm inspecting real XML return doc
Show this thread
End of conversation
New conversation -
-
-
This Tweet is unavailable.
-
Yes there is usually a more sensible intermediary form. No it's not the fault of XML that it isn't the primary form, that's the fault of the whoever designed the 'overwrought' format.
End of conversation
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.