GUIs - ruby on rails, rico

David Hopwood david.nospam.hopwood@REDACTED
Wed Sep 21 22:12:37 CEST 2005

Shawn Pearce wrote:
> "Joe Armstrong (AL/EAB)" <joe.armstrong@REDACTED> wrote:
>>    BTW - why is it called XMLHTTP? - as far as I can see there is absolutly no
>>requirement for the server responding to requests with XML - the server can reply with
>>any old string that it feels like, and a javascript receptor can do anything
>>it feels like with the result.
> Because XML is coooooool.  Or something like that.  Management will
> purchase anything with a hot buzzword in it, if they had just
> called it HTTPRequest it wouldn't have gotten management buy-in,
> as everything was about XML at the time.

Why would it need to get management buy-in? This is low-level stuff that should
be left to the techies in any sanely run company...

(...oh, right, I see what assumption I'm making ;-)

> SOAP was especially cool around 1999.  But SOAPHTTPRequest might have been
> considered to be too specific, so XMLHTTPRequest it is...
> Why is Erlang called Erlang?  :-)


> Why is Internet Explorer not called Automatic Virus Downloader?


David Hopwood <david.nospam.hopwood@REDACTED>

More information about the erlang-questions mailing list