[jira] [Updated] (CAMEL-8116) Allow more control of message splitting policy

2015-01-09 Thread Claus Ibsen (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-8116:
---
Fix Version/s: 2.14.1

 Allow more control of message splitting policy
 --

 Key: CAMEL-8116
 URL: https://issues.apache.org/jira/browse/CAMEL-8116
 Project: Camel
  Issue Type: Improvement
  Components: camel-smpp
Affects Versions: 2.14.0
Reporter: Daniel Pocock
Assignee: Claus Ibsen
Priority: Minor
 Fix For: 2.14.1, 2.15.0


 Currently, camel-smpp splits a long message into 140 byte SMS messages to go 
 over the network.  This is done automatically for any long message.
 Not all networks support these split messages.  Some networks drop the 
 subsequent frames after the first, some don't delivery anything.
 It would be useful to give users of the component the ability to set a 
 message splitting policy, e.g. to refuse to split messages and throw an 
 exception if a long message is encountered.  This will reduce load on the 
 SMPP provider and may also avoid costs associated with messages that are 
 never delivered.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (CAMEL-8116) Allow more control of message splitting policy

2014-12-03 Thread Claus Ibsen (JIRA)

 [ 
https://issues.apache.org/jira/browse/CAMEL-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-8116:
---
Fix Version/s: 2.15.0

 Allow more control of message splitting policy
 --

 Key: CAMEL-8116
 URL: https://issues.apache.org/jira/browse/CAMEL-8116
 Project: Camel
  Issue Type: Improvement
  Components: camel-smpp
Affects Versions: 2.14.0
Reporter: Daniel Pocock
Priority: Minor
 Fix For: 2.15.0


 Currently, camel-smpp splits a long message into 140 byte SMS messages to go 
 over the network.  This is done automatically for any long message.
 Not all networks support these split messages.  Some networks drop the 
 subsequent frames after the first, some don't delivery anything.
 It would be useful to give users of the component the ability to set a 
 message splitting policy, e.g. to refuse to split messages and throw an 
 exception if a long message is encountered.  This will reduce load on the 
 SMPP provider and may also avoid costs associated with messages that are 
 never delivered.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)