Return-Path: Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm Delivered-To: mailing list axis-user@xml.apache.org Delivered-To: moderator for axis-user@xml.apache.org Received: (qmail 48608 invoked from network); 9 Apr 2002 00:39:23 -0000 Received: from unknown (HELO dnmx1.obizi.com) (63.102.81.233) by daedalus.apache.org with SMTP; 9 Apr 2002 00:39:23 -0000 Received: from dnobizimail1.openbiz.biz (IDENT:root@dnobizimail1.openbiz.biz [172.20.0.140]) by dnmx1.obizi.com (8.11.0/8.11.0) with ESMTP id g38NcYm02228 for ; Mon, 8 Apr 2002 17:38:34 -0600 Received: from wdn086 (poseidon.meredith.com [172.20.2.225] (may be forged)) by dnobizimail1.openbiz.biz (8.9.3/8.9.3) with SMTP id SAA08186 for ; Mon, 8 Apr 2002 18:38:09 -0600 Reply-To: From: "ajack" To: Subject: RE: style="document" rulz! Date: Mon, 8 Apr 2002 18:40:04 -0600 Message-ID: <000701c1df5f$17187310$5b18730a@wdn086> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal In-Reply-To: <000801c1df5a$06672c00$ae04560c@DELL850> Disposition-Notification-To: "ajack" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Stan Jordan [mailto:skjordan@worldnet.att.net] wrote: > Subject: style="document" rulz! > And style="rpc" sucks! > To learn why, read this... > http://www.fawcette.com/xmlmag/2002_04/magazine/departments/endtag/ The author presupposes that having two applications "work" when they get out of synch is a good thing. I'd call that "silently failing". Personally, I'll accept if my HTML is presented quite as the remote author intended, but I'm not so sure I'd like my banking application (or insert any business use here) be so "tolerant" to miscommunication. Since WSDL allows for explicit & communication of the new interface (hopefully commented with version changes, but fat chance I know since WSDL is typically computer generated) I'd rather things break and I get the chance to re-evaluate. That -- and/or preserve the old interface, and allow the new interface for new clients. XML is not some magic glue that understands when things change. It might still allow a non-validating [or even validating, if remote schema] parse, and XPath may still access elements, but the application will not understand the change, and that could be very bad. Also -- having spent the last N hours trying to get "document style" to work I sure like the simplicity of explicit "tight" RPC. :-) regards, Adam