Let's simplify it by sending the op name in both cases .. if the ping method needs the AO it can go look it up.
Sanjiva. On Thu, 2007-02-15 at 13:09 +0530, Thilina Gunarathne wrote: > Sameera, > According to your diagram I get the feeling that the Pingable > interface is going to have two overloaded Ping methods with one having > AxisOperation as the parameter & String (operation name) as the > parameter for the other one.. > > In this case I would like to see two interfaces.. > > Thanks, > Thilina > > > On 2/15/07, Sameera Madushan <[EMAIL PROTECTED]> wrote: > > Hi, > > > > On 2/13/07, Paul Fremantle <[EMAIL PROTECTED]> wrote: > > > If you really want to make sure there is a consistent interface, then > > > we can return a value that identifies what level of ping succeeded: > > > > > > 0 - ping failed > > > 1 - ping worked at module level > > > 2 - ping worked at MR level, plus module level > > > 3 - ping worked at service level, MR and module level. > > > > > > > Using the above levels, How "ping" works can be illustrated as in > > attached diagram. The PingHandler is registered in the Dispatch phase, > > before InstanceDispatcher handler. > > > > Sameera > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- Sanjiva Weerawarana, Ph.D. Founder & Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ Director; Open Source Initiative; http://www.opensource.org/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
