What's the difference between these two articles, which are over 10 years apart: "Web 2.0, REST and BEA Workshop"  and On-Line Componentware . Not an awful lot.
I still have the Byte issue in which Jon Udell talked about calling AltaVista using a Perl Script. It's an issue with "Java Chips" on the cover, and it's sitting in a box in an attic in north Dublin. Jon Udell's column talked about calling a URL programmatically by passing parameters in a Query-String, and then parsing the HTML results into Perl variables. In the BEA example, the data comes back as XML and is parsed using Java. But the principle is the same.
For me, that Byte article was important because it bridged the world of programming / distributed computing (which I'd learnt about in college) and the world of the Web (which was taking off then, but was mostly focussed around publishing and graphic design). I used the idea in Jon Udell's article to design systems for the Irish Government (in 1998) and for Intel (in 1999), calling a same URL via a scriptable Java applet in a browser and via a C++ MFC application. But back then we didn't call it "REST" or and we didn't call that Web component which we called from multiple heterogenous clients a "Web Service".
It's interesting that the whole "Web Services = SOAP" thing has gone so far that BEA has to remind people that you can use their products to go a simple HTTP GET, something you could easily do 10 years ago! Mark Baker had it right in 2003 when he said: "There are a whole lot of REST tool kits available, it's just that people don't know what they are".