Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 63067 invoked from network); 19 Jun 2008 04:33:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Jun 2008 04:33:06 -0000 Received: (qmail 6206 invoked by uid 500); 19 Jun 2008 04:33:07 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 6196 invoked by uid 500); 19 Jun 2008 04:33:07 -0000 Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C User List" Reply-To: "Apache AXIS C User List" Delivered-To: mailing list axis-c-user@ws.apache.org Received: (qmail 6185 invoked by uid 99); 19 Jun 2008 04:33:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2008 21:33:07 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.68.5.16] (HELO relay02.pair.com) (209.68.5.16) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 19 Jun 2008 04:32:18 +0000 Received: (qmail 88220 invoked from network); 19 Jun 2008 04:31:33 -0000 Received: from unknown (HELO ?127.0.0.1?) (unknown) by unknown with SMTP; 19 Jun 2008 04:31:33 -0000 X-pair-Authenticated: 203.115.29.243 Message-ID: <4859E125.6070805@wso2.com> Date: Thu, 19 Jun 2008 10:01:33 +0530 From: Danushka Menikkumbura User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Apache AXIS C User List Subject: Re: AXIS2C Asynchronous Handling.. References: <000001c8d1c1$88079230$750218ac@LGE.NET> In-Reply-To: <000001c8d1c1$88079230$750218ac@LGE.NET> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org > Can anyone please send the implementation details (service sample > files) reference for handling the asynchronous client request�s? > > Shobha, The asynchronous/synchronous behavior is solely handled on the client side. The service implementation is done irrespective of the async/sync dual-channel/single-channel behavior on the client side. Just refer to axis2c\samples\user_guide\clients\echo_non_blocking.c to see how you do async/single-channel calls on the client side. Danushka --------------------------------------------------------------------- To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org For additional commands, e-mail: axis-c-user-help@ws.apache.org