[
https://issues.apache.org/jira/browse/CAMEL-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994158#comment-12994158
]
Christian Müller commented on CAMEL-3656:
-----------------------------------------
Jaco, which sample do you mean? The AsyncSubmitReceiveDeliverSmExample sample
send the short messages synchronous and receive the DeliveryReceipt
asynchronous. But this is already implemented in camel-smpp.
In my opinion, jsmpp didn't support this feature out of the box. We could only
increase the throughput if we send the short message in it's own thread and
using the [Asynchronous Routing
Engine|http://camel.apache.org/asynchronous-routing-engine.html] to propagate
the messageId back to the caller. I think this is a bit more complicated to
implement, but I will try it...
Christian
> SMPP - Add support for Asynchronous smpp interaction
> ----------------------------------------------------
>
> Key: CAMEL-3656
> URL: https://issues.apache.org/jira/browse/CAMEL-3656
> Project: Camel
> Issue Type: New Feature
> Components: camel-smpp
> Affects Versions: 2.6.0
> Reporter: Jaco van Tonder
> Assignee: Christian Müller
> Labels: smpp
>
> Add support for asynchronous delivery from camel-smpp to the SMSC endpoint.
> This allows for better throughput to the SMSC, meaning messages will get
> delivered in higher volumes.
> The end user should be allowed to supply the following configurables:
> * asynchronous = [true,false]
> * Maximum number of outstanding messages.
> * ?
> The jSMPP code has a pretty neat example on how to implement asynchronous
> sending.
> We might have to re-think how we will tie back the message id's, as those
> will not be available immediately in the same way that the synchronized
> sending makes them available.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
