Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 64572 invoked from network); 16 Nov 2004 20:25:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 16 Nov 2004 20:25:21 -0000 Received: (qmail 48659 invoked by uid 500); 16 Nov 2004 20:25:12 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 48634 invoked by uid 500); 16 Nov 2004 20:25:12 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 48619 invoked by uid 99); 16 Nov 2004 20:25:11 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [213.63.185.197] (HELO ruiveloso.100limite.pt) (213.63.185.197) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 16 Nov 2004 12:25:06 -0800 X-ClientAddr: 127.0.0.1 Received: from 04web.com (localhost.localdomain [127.0.0.1]) (authenticated (0 bits)) by ruiveloso.100limite.pt (8.11.6/8.11.6) with ESMTP id iAGKOxe29496 for ; Tue, 16 Nov 2004 20:24:59 GMT Received: from pcppeusof04.cern.ch ([137.138.78.62]) (SquirrelMail authenticated user salgado.pc@04web.com) by www.04web.com with HTTP; Tue, 16 Nov 2004 20:24:59 -0000 (WET) Message-ID: <4944.137.138.78.62.1100636699.squirrel@www.04web.com> Date: Tue, 16 Nov 2004 20:24:59 -0000 (WET) Subject: Re: Signal to noise ratio in Soap is very high From: To: In-Reply-To: <419A623D.6040206@drexel.edu> References: <419A26DF.8090304@drexel.edu> <419A3D6E.7050403@commerce.state.ak.us> <419A623D.6040206@drexel.edu> X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.11) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-ruiveloso-mailscan-info: For more information please contact postmaster@100limite.com X-ruiveloso-mailscan: Clean X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I read an article about Fast Web Services... but I think there was no new development since then. http://java.sun.com/developer/technicalArticles/WebServices/fastWS/ > > Thank you for the responses. I think it's possible to achieve > interoperability and small foot print. It's just Soap was designed > lousy in this particular aspect. When saying if speed matters, I think > most of the apps that has some kind of communication, speed does > matter. I think there should be a new standard/version to replace Soap > if this cannot be addressed. > > Paul Callahan wrote: > >>I second that... And would just add that you might want to think about >> when your application is just too 'chatty' for SOAP... >> >>-pc >> >>On Tue, 16 Nov 2004 08:48:30 -0900, Elaine Nance >> wrote: >> >> >>>SOAP is not designed to create compact dataflows. It is designed for >>> interoperability and, because it is XML, extensibility. >>>IMHO, I would *not* use SOAP for purely internal processes if >>>speed or stream size matters (where faster/smaller) is better. >>> >>>In that case I would go strictly with a socket-level approach. >>> >>>Just my 2 small coins, >>>Elaine >>> >>> >>> >>>Vy Ho wrote: >>> >>> >>>>I look at a message send back from the server to a client in Axis, >>>> and was very surprised that most of the text is not the data that I >>>> need to send, but declaration and long namspaces. Is it possible to >>>> reduce these down and still comply with Soap? >>>> >>>>Thanks, >>>> >>>>vh >>>> >>>> >>>> >>><~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> | Computers are useless. They can only give you answers. >>> | -- Pablo Picasso -- >>><~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>> >>> >>> >>>