Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 65149 invoked by uid 500); 17 May 2001 01:56:34 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 65142 invoked from network); 17 May 2001 01:56:32 -0000 Received: from mta6.snfc21.pbi.net (206.13.28.240) by h31.sny.collab.net with SMTP; 17 May 2001 01:56:32 -0000 Received: from speedball ([216.102.90.148]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with SMTP id <0GDG008IQIPVP0@mta6.snfc21.pbi.net> for axis-dev@xml.apache.org; Wed, 16 May 2001 18:56:20 -0700 (PDT) Date: Wed, 16 May 2001 18:59:00 -0700 From: Rob Jellinghaus Subject: Re: Use-cases for Services In-reply-to: X-Sender: robj@shell2.ba.best.com To: axis-dev@xml.apache.org, axis-dev@xml.apache.org Message-id: <3.0.1.32.20010516185900.010e4180@shell2.ba.best.com> MIME-version: 1.0 X-Mailer: Windows Eudora Light Version 3.0.1 (32) Content-type: text/plain; charset="us-ascii" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N At 03:58 PM 5/14/2001 -0400, gdaniels@macromedia.com wrote: >1) invoke() or send()? invoke() >2) Should we support asynchronous request/response messaging, i.e.: > s.invokeAsync(message, callback); It's pretty easy to implement that on top of Axis (just wrap a thread around the synchronous invoke, and call the callback when the return comes in). I don't know that Axis needs this yet. >3) Does this look like a reasonable start for where we want to be? Yes. Cheers, Rob