Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (herse.apache.org: domain of sameera.madushan@gmail.com
 designates 64.233.182.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=PDdj53NK1q0vzs89r6DHsUkwni781iP224W+bkP3tQKyNBgSUquhiwuDH2vOff1x9kPpE7kJ4JKPt2SXQUifVrWyraYBcqaLTKkeRw3ynXeeKXqJ05QnQmemriULfth5HQn2xsiFFRA8bC9ZJIWHta5/CKxkHfVd9X3CnocThHk=
Message-ID: <4f5c8bd80702082248w7fdde606w9d6ff6b581255686@mail.gmail.com>
Date: Fri, 9 Feb 2007 12:18:55 +0530
From: "Sameera Madushan" <sameera.madushan@gmail.com>
To: axis-dev@ws.apache.org
Subject: Re: [axis2] Pinging capability to services deployed in Axs2
In-Reply-To: <45CC13A7.7020608@opensource.lk>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_25878_12339297.1171003735246"
References: <4f5c8bd80702061028r63b03ba6r9c4dddb2c2890fb1@mail.gmail.com>
	 <45C9551C.5030408@opensource.lk>
	 <4f5c8bd80702062129q299a3bd5j8f06e3c915f50cc8@mail.gmail.com>
	 <45CA9A6C.4080400@sosnoski.com>
	 <1170979109.21422.11.camel@localhost.localdomain>
	 <45CC13A7.7020608@opensource.lk>

------=_Part_25878_12339297.1171003735246
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi deepal,

>
> >The problem is that pinging at the handler level basically amounts to
> >just asking "is there such a service?". Having it go to the message
> >receiver allows the ping to be responded to based on more useful data-
> >such as did the impl class or script or whatever load etc.. So its
> >really a question of fidelity- yes some level of liveness checking can
> >be done at a handler level but you get much improved info by getting the
> >ping to the message receiver.
> >
> >
> Service might have more than one MRs (most of the time it does) so
> checking only one MR wont give you the accurate results.  The other
> problem I have is which MR you are going to call when you receive a ping
> request , are you going call all the MRs or only one.


There can be two types of ping requests.

1. Service level ping requests.
2. Operation level ping requests.

In the first case, you are correct, we need to ping all the operations
within the service. Then in the ping response simply we can say whether the
service is up or not, or we can include all operations and their status.

In the second case we can directly ping the MR assinged to the requested
operation and the response accordingly.

This implies that we need to develop a schema for the ping requests and ping
responses.

thanks
Sameera.

------=_Part_25878_12339297.1171003735246
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi deepal,<br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>&gt;The problem is that pinging at the handler level basically amounts to
<br>&gt;just asking &quot;is there such a service?&quot;. Having it go to the message<br>&gt;receiver allows the ping to be responded to based on more useful data-<br>&gt;such as did the impl class or script or whatever load etc.. So its
<br>&gt;really a question of fidelity- yes some level of liveness checking can<br>&gt;be done at a handler level but you get much improved info by getting the<br>&gt;ping to the message receiver.<br>&gt;<br>&gt;<br>Service might have more than one MRs (most of the time it does) so
<br>checking only one MR wont give you the accurate results.&nbsp;&nbsp;The other<br>problem I have is which MR you are going to call when you receive a ping<br>request , are you going call all the MRs or only one.</blockquote><div>
<br>There can be two types of ping requests.<br><br>1. Service level ping requests.<br>2. Operation level ping requests.<br><br>In the first case, you are correct, we need to ping all the operations within the service. Then in the ping response simply we can say whether the service is up or not, or we can include all operations and their status.
<br><br>In the second case we can directly ping the MR assinged to the requested operation and the response accordingly.<br><br>This implies that we need to develop a schema for the ping requests and ping responses.<br><br>
thanks<br>Sameera.<br></div><br></div><br>

------=_Part_25878_12339297.1171003735246--