You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Srinath Perera <he...@gmail.com> on 2005/11/04 17:40:11 UTC
[Axis2]New Feature - Sending same message to more than One Recepcient
Hi All;
Shall we add a support to users to send same message to more than one
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 will
be very expensive and if we do the thingy inside Axis2 we can set the
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
Re: [Axis2]New Feature - Sending same message to more than One Recepcient
Posted by Srinath Perera <he...@gmail.com>.
Hi Christoph;
If you can tell us what was your experiance and something about what
is exactly you look for. e.g. the Ideal API you want to see. It will
be very helpful :)
e.g 1) Do you need to send differnat addressing headers
2) do you need differant aspects (WS-Secuirty .. RM ) for each receiption
3) What are the informatio you would like to control via API
cheers
Srinath
On 11/4/05, Christoph Langguth <ch...@umit.at> wrote:
> Srinath Perera schrieb:
> > Hi All;
> >
> > Shall we add a support to users to send same message to more than one
> > 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 will
> > be very expensive and if we do the thingy inside Axis2 we can set the
> > 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?
>
> Hi all,
>
> while I'm neither an Axis2 developer nor really into the architectural
> or implementation details, I would love to have such a feature; I have
> actually been looking for exactly this a few weeks ago, ending up with
> no viable solution.
>
> So, a very strong YES from my side :-)
>
> Cheers,
> Christoph
>
Re: [Axis2]New Feature - Sending same message to more than One Recepcient
Posted by Christoph Langguth <ch...@umit.at>.
Srinath Perera schrieb:
> Hi All;
>
> Shall we add a support to users to send same message to more than one
> 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 will
> be very expensive and if we do the thingy inside Axis2 we can set the
> 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?
Hi all,
while I'm neither an Axis2 developer nor really into the architectural
or implementation details, I would love to have such a feature; I have
actually been looking for exactly this a few weeks ago, ending up with
no viable solution.
So, a very strong YES from my side :-)
Cheers,
Christoph
Re: [Axis2]New Feature - Sending same message to more than One Recepcient
Posted by Srinath Perera <he...@gmail.com>.
Hi All;
My feeling is
1) We must support differant Adressing Headers for different users
2) May be we need to support different Handlers for different
consumers. (Or we shall call we do not do it and my be in Axis3 ;) ..
)
What I thought was to not to changes present SOAP processing Model and
only write a new MultiOutMepClient that takes list of addresses and
send them to different users.
If we support #1 only we need to run the Handler Chain (Pipe) once ..
or we if support #1 and #2 we need to re run the HandlerChain once per
each consumer.
I prefer supporting #1 and #2
In all cases we could set OM cache true and use one SOAP body OM for
all requests!
thoughts?
Thanks
Srinath
On 11/7/05, Chathura Herath <ch...@gmail.com> wrote:
> 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 <aj...@gmail.com> wrote:
> > Hi All,
> > Here's my view on this. If I remember right there was some discussion way
> > back on this and it ended up with the understanding that something like this
> > ends up with a pub-sub architecture. So what I think is that this
> > multiplexing could be handled as a different transport which abstracts all
> > 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 <ch...@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 <ch...@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 one
> > > > >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 will
> > > > >be very expensive and if we do the thingy inside Axis2 we can set the
> > > > >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
>
Re: [Axis2]New Feature - Sending same message to more than One Recepcient
Posted by Chathura Herath <ch...@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 <aj...@gmail.com> wrote:
> Hi All,
> Here's my view on this. If I remember right there was some discussion way
> back on this and it ended up with the understanding that something like this
> ends up with a pub-sub architecture. So what I think is that this
> multiplexing could be handled as a different transport which abstracts all
> 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 <ch...@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 <ch...@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 one
> > > >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 will
> > > >be very expensive and if we do the thingy inside Axis2 we can set the
> > > >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
Re: [Axis2]New Feature - Sending same message to more than One Recepcient
Posted by Ajith Ranabahu <aj...@gmail.com>.
Hi All,
Here's my view on this. If I remember right there was some discussion way
back on this and it ended up with the understanding that something like this
ends up with a pub-sub architecture. So what I think is that this
multiplexing could be handled as a different transport which abstracts all
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 <ch...@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 <ch...@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 one
> > >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 will
> > >be very expensive and if we do the thingy inside Axis2 we can set the
> > >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
Re: [Axis2]New Feature - Sending same message to more than One Recepcient
Posted by Chathura Herath <ch...@gmail.com>.
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 <ch...@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 one
> >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 will
> >be very expensive and if we do the thingy inside Axis2 we can set the
> >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
Re: [Axis2]New Feature - Sending same message to more than One Recepcient
Posted by Eran Chinthaka <ch...@opensource.lk>.
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 one
>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 will
>be very expensive and if we do the thingy inside Axis2 we can set the
>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
>
>
>
>