camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <>
Subject Re: SMPP single session (producer+consumer)
Date Fri, 21 Oct 2011 21:27:50 GMT
Hello Ioannis, hello Peter!

If we create the session, we have to bind it as receiver, transmitter or
transceiver. At the moment we bind it as receiver (consumer -
from("smpp://")) or transmitter (producer - to("smpp://")).

If we bind it as transceiver, the user have to create a route like:


and "direct:X" will be called after the short message was sent *AND* when a
new deliver notification arrived *AND* for an incoming short message. This
means the user have to define a choice to distinguish the different cases.


Looks not really nice.

But what should happen, when the user define the route like this?


and we receive the deliver notifications or an incoming short message?
Should we throw an exception?


On Fri, Oct 21, 2011 at 9:54 AM, Ioannis Canellos <> wrote:

> Here are some thoughts.
> Currently the producer and consumer of the smpp endpoint create their own
> sessions. If the sessions were handled by the endpoint itself we may were
> able to have a producer and consumer use the same smpp session. This would
> probably allow us to consume messages (deliversm) from the same session we
> use to produce (submitsm). This would also open the way to
> bind transceivers too.
> @Christian, do you think that something like this makes sense?
> --
> *Ioannis Canellos*
> *
> FuseSource <>
> **
> Blog:
> **
> Apache Karaf <> Committer & PMC
> Apache ServiceMix <>  Committer
> Apache Gora <> Committer
> *

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message