|
Updated: 9/1/2002; 7:00:46 PM.
 |
Thursday, April 18, 2002 |
Ugo Cei: Bloogle! Click on the "Google It!" link below to see the Google Web APIs called from Cocoon via the SOAP taglib. All is done using existing Cocoon components, no ad-hoc actions or generators. Cocoon rocks!
10:35:11 PM 
|
|
Jon: Last night, I had dinner with Dale Dougherty, who has been around the track a few times when it comes to processing structured text. (Dale wrote the 1990 classic, sed and awk.) What bugs him lately? Overly complex XML schemas. Less is more, he has concluded. Ever typed "man awk" lately? In particular, look at the sheer number of command line options.
P.S. I'm a big fan of sed, as well as one of awk's progeny: Perl.
Update: Seeing Jon's response, I guess I wasn't clear. Command line options are, in my mind, the equivalent of global variables.
8:50:49 PM
|
|
Ingo, Simon, and Peter announce .Net Remoting related Open Source projects. First two are Jabber and SMTP support. Bidirectional TCP, XML-RPC, MSN Messenger, Caching, and other ideas are planned. Excellent license.
8:19:32 PM
|
|
Thomas Wagner: Javascript ... I'm slow today so I'm not catching on. Try clicking on this link. My point was that the browser of your choice likely has supported switch statements on strings for quite some time.
3:24:29 PM
|
|
Ed Dumbill: SOAP? Bah! What's wrong with /bin/sh?
11:28:29 AM
|
|
Gordon Weakliem: I asked if Sun had released interop results for the WSDP, the rep said he didn't know of any. And will Apache be changing all their namespaces to javax.SOAP? Furthermore, is stardardization necessary? Apache Axis implements the javax.xml.soap interfaces. And, yes, standardization is necessary so that you can replace the implementation you get with one that does participate in the interop activities.
9:33:02 AM
|
|
[XMLHack] Amazon goes REST, Google goes SOAP. Without having seen the DTD, and based solely on Simon St.Laurent's article, it seems to me that a WSDL could be produced which uses http:binding verb="GET" and soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document", much like the default mappings that .NET provides today.
So: both company's protocols are layered over HTTP. All verbs are stateless. Both are based at least partly on XML. If you accept Roy's interpretation of REST as a strictly an architectural style, both are REST to various degrees and both are request/response.
Amazon's interface may be more suitable for traditional approaches to caching (though requesting that developers limit themselves to once per day per query effectively nullifies this). Amazon's interface may also be simpler in the starting-from-zero sense. But as Google's interface builds upon infrastructure that is widely deployed, the net effort to get started is may be less for many. Significantly less.
5:33:47 AM
|
|
|
