Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Mon, 24 Oct 2011 22:14:32 +0000 (UTC)
From: =?utf-8?Q?Christian_M=C3=BCller_=28Updated=29_=28JIRA=29?=
 <jira@apache.org>
To: dev@camel.apache.org
Message-ID: 
 <1244657852.10919.1319494472248.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1851680032.10251.1297420017383.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CAMEL-3656) SMPP - Add support for Asynchronous
 smpp interaction
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CAMEL-3656?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian M=C3=BCller updated CAMEL-3656:
------------------------------------

    Fix Version/s:     (was: 2.9.0)
                   Future
   =20
> 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=C3=BCller
>              Labels: smpp
>             Fix For: Future
>
>
> Add support for asynchronous delivery from camel-smpp to the SMSC endpoin=
t.
> 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 =3D [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 se=
nding makes them available.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira