You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/01/17 12:09:35 UTC
[jira] [Updated] (CAMEL-8240) camel-apns should allow custom
expiration times so that users get fine grained expiration control for
mobile push messages
[ https://issues.apache.org/jira/browse/CAMEL-8240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-8240:
-------------------------------
Fix Version/s: 2.15.0
> camel-apns should allow custom expiration times so that users get fine grained expiration control for mobile push messages
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-8240
> URL: https://issues.apache.org/jira/browse/CAMEL-8240
> Project: Camel
> Issue Type: New Feature
> Components: camel-apns
> Affects Versions: 2.14.1
> Reporter: Justin Heesemann
> Assignee: Willem Jiang
> Priority: Minor
> Fix For: 2.15.0
>
>
> Currently it is not possible to send apns messages with a user defined expiration date.
> This affects both STRING and PAYLOAD message types.
> The org.apache.camel.component.apns.ApnsProducer calls the ApnsService.push(Collection<String> deviceTokens, String payload) throws NetworkIOException;
> method which uses a EnhancedApnsNotification.MAXIMUM_EXPIRY (somewhen in 2038).
> A possible solution would allow the usage of a new ApnsConstants.HEADER_EXPIRY message header where users could store the wanted expiration time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)