Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (asf.osuosl.org: domain of chathurah@gmail.com designates
 66.249.82.195 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=V2YWK9HZ9etIHSD5ExOoPhYbdJXXKsWVo/CqLInP56vCJP9cb4DrDSTPwvsVq7aTAxgZJiGUUmyuXWkxBOXQv6tMYKu2NwrOLXpzHfvh+RFTOPVUWjVRACZG8eYGKl4HZ28Ef7JS9jf73ud5aKc5GDnNAQN/gy5kg8J0Mv33/Ls=
Message-ID: <3ce57c850511062106v1ff8238dg7ab54c8fbe72c9a1@mail.gmail.com>
Date: Mon, 7 Nov 2005 00:06:10 -0500
From: Chathura Herath <chathurah@gmail.com>
To: axis-dev@ws.apache.org
Subject: Re: [Axis2]New Feature - Sending same message to more than One
 Recepcient
In-Reply-To: <f43ea5790511051138j6da97ba2rc334fd3d9dc32358@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <f8de7ee0511040840kff54b6y8cefe1152aec0df0@mail.gmail.com>
	 <436C4651.7090103@opensource.lk>
	 <3ce57c850511042332p6c665159tbb30c7c410da37c5@mail.gmail.com>
	 <f43ea5790511051138j6da97ba2rc334fd3d9dc32358@mail.gmail.com>

Not that straight forward. How would you handle addressing which is
part of the soap processing model in a transport. In my view other QOS
are out of the question if you want to do multiplexing.
Chathura

On 11/5/05, Ajith Ranabahu <ajith.ranabahu@gmail.com> wrote:
> Hi All,
>  Here's my view on this. If I remember right there was some discussion wa=
y
> back on this and it ended up with the understanding that something like t=
his
> ends up with a pub-sub architecture. So what I think is that this
> multiplexing could be handled as a different transport which abstracts al=
l
> addressing and other QOS issues. The particular transport sender also
> handles subscriptions so Axis wouldn't know anything about it!
>
>
>
> On 11/5/05, Chathura Herath <chathurah@gmail.com> wrote:
> > Actually i am trying to implement this kind of transport multiplexing
> > thing for some other project and one further problem that i faced was
> > how to handle the addressing stuff. So IMO multiplexing should start
> > at the addressing out handler because the addressing headers are
> > different for the out going messages. This is kind of messy though and
> > kills the grace of the SOAP processing model. Further the nice
> > application for this, which would be WS-notification and WS-Eventing
> > both have ws addressing around.
> >
> > Actually Eran think of a Notification framework where you have 20
> > Notification consumers. So instead of making 20 call invocations we
> > can write a transport (or an addressing handler) such that it will
> > deliver the same message to the different Notification consumers(20).
> > call.setToList(eprList);
> > call.invokeBlocking(...)
> >
> >   So the message will go through the soap processing model only once.
> > So only one OM for the most part. There are other complications like
> > different consumers requiring different policies, but from my personal
> > experience of Notification and eventing i know that almost all the
> > notifications that are sent out are same except for the addressing
> > headers.
> >
> > Believe me this feature would come in handy when we eventually
> > implement Notification and eventing.
> >
> > Chathura.
> >
> > On 11/5/05, Eran Chinthaka <chinthaka@opensource.lk> wrote:
> > > Hi Srinath,
> > >
> > > can't wedo this by changing the toEPR in the Call api and invoke the
> > > method ? Sorry if I understood this wrong.
> > >
> > > for example;
> > > call.setTo(eprOne)
> > > call.ivokeBlocking(.....);
> > >
> > > call.setTo(eprTwo)
> > > call.invokeBlocking(...)
> > >
> > >
> > >
> > > Srinath Perera wrote:
> > >
> > > >Hi All;
> > > >
> > > >Shall we add a support to users to send same message to more than on=
e
> > > >recipients?
> > > >
> > > >Motivate for the doing this is if we need to send same message to 20
> > > >recipients, (e.g. Publish Subscribe) . If user create 20 Calls it wi=
ll
> > > >be very expensive and  if we do the thingy inside Axis2 we can set t=
he
> > > >OM caching true and reuse at least part of the Message to multiple
> > > >invocations.
> > > >
> > > >I do not feel this should be done at the transport sender level (e.g=
.
> > > >We need different addressing properties). I feel we should have
> > > >different Pipe for each while sharing the same SOAP Body. I think
> > > >about something like MultiOutClient (or PublisherClient .. I am not
> > > >sure ) add to Client API
> > > >
> > > >I am thinking aloud :), this could actually get very complex
> > > >thoughts?
> > > >
> > > >Thanks
> > > >
> > > >Srinath
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > Chathura Herath
> > http://www.bloglines.com/blog/chathurah
> >
>
>
>
> --
> Ajith Ranabahu


--
Chathura Herath
http://www.bloglines.com/blog/chathurah