Hey Jason, This looks good. Here are a few tips that might help from our current production usage.
1) Most people don't send directly to devices. They usually send to groups or users. The devices are registered to the user via the api, and then they're sent either to the user directly, or a group of users that have devices attached. 2) We had issues with the apns during heavy load. We filed an issue, and it appears someone has documented a workaround. This is why we migrated to the pushy library instead. https://github.com/notnoop/java-apns/issues/134 This sounds like a great contribution, Good Luck! Todd On Thu, Aug 14, 2014 at 8:39 PM, <jas...@apps4u.com.au> wrote: > Hi I've come up with the design on how I'm adding push messaging so If any > one how intrested is using this or having it added to main repo please > comment on design any idea are welcome . > > 1- push message notifiers will be attached to groups and each application > will get a default notifier that will message all devices for the > application (no need to create two notifier just to message iOS or android). > > 2- will add a push messaging service to the services module. > > 3 - will add a messaging endpoint to the REST module. (for registering > device for push and for trigger , etc) > > 4 - will add some tests to test service and rest code. > > 5 - will add to android and iOS sdks so device can handle push and > register for push. > > Im also starting with HTTP access to Android push messaging if I have time > or at a latter time I'll add CCS (XMPP) . > > One thing Ive not decided on is if we should add a Model File to the Core > module any input on that would be helpful . > > Please fell free to look at my fork on bitbucket as the we work on this Im > hoping this won't take more then a week Ive put two other guys on it with > my self. all are welcome to comment, help ,etc > > > Will use com.notnoop.apns and google.gcm.server > > > August 14 2014 2:01 PM, jas...@apps4u.com.au wrote: > > that Ok Ive started mine yesterday and engaged 2 programmers yesterday > to start so I know I'll be > > done within a week . So I'll leave to other to decide wether they take > my pull request. I don't > > know your timeline is but with out push this is really not something > that can be called turnkey as > > its the most requested feature of and mobile BaaS. Also I don't really > like having two different > > notifiers for one application one for iOS and one for Android . It would > be easy to integrate this > > with AWS message service as it has the same feature as APIGee push > messaging. Which I thought was > > just AWS SNS. > > > > August 14 2014 1:01 AM, "Todd Nine" <todd.n...@gmail.com> wrote: > > > >> Hey Jason, > >> We've already build this at Apigee. We're in the process of contributing > >> it back, but I'm not sure on the timeline of this. It's stable and been > in > >> production use for some time. Below is the documentation and the API > >> overview. > >> > >> http://apigee.com/docs/app-services/content/push-notifications-overview > >> > >> We've found our api works well and it's easy for our users to understand > >> and get set up. Internally, we're using our scheduler to perform large > >> batch delivery, and the master/worker distribution semantics to increase > >> the delivery throughput. > >> > >> For the push clients, we're using these libraries > >> > >> iOs > >> > >> https://github.com/relayrides/pushy/tree/master > >> > >> Android > >> > >> https://developer.android.com/google/gcm/client.html > >> > >> Let me know if you have any more question. > >> > >> Later, > >> Todd > >> > >> On Wed, Aug 13, 2014 at 12:11 AM, Matthias Wessendorf < > mat...@apache.org> > >> wrote: > >> > >>> On Wed, Aug 13, 2014 at 7:57 AM, <jas...@apps4u.com.au> wrote: > >>> > >>>> I was thinking that I would use these two packages as Ive got existing > >>>> code using these two libraries and Ive got client side code that would > >>> > >>> not > >>>> take long to add the the ios and Android SDK's that was I get auth for > >>> > >>> free > >>>> from the sdk's & usergrid and the queue server can be a option either > >>>> iron.io or beanstalk . > >>>> > >>>> com.google.android.gcm.server > >>>> > >>>> http://notnoop.github.com/java-apns > >>> > >>> yep - we, internally, use the same bits > >>> > >>>> August 13 2014 3:44 PM, jas...@apps4u.com.au wrote: > >>>>> Im get one of my team members to download your code and have a look > >>>> weather this would could be > >>>>> integrated into usergrid. > >>>>> > >>>>> August 13 2014 3:36 PM, "Matthias Wessendorf" <mat...@apache.org> > >>> > >>> wrote: > >>>>> > >>>>>> Hello Jason, > >>>>>> > >>>>>> perhaps you can integrate our UnifiedPush Server (e.g. running on a > >>>>>> different box, or on Openshift). > >>>>>> It supports the concept of "Application": > >>>>>> > >>> > >>> > > > http://staging.aerogear.org/docs/unifiedpush/ups_userguide/admin-ui/#_sending_a_push_notification > >> > >>>>>> > >>>>>> You can even narrow down to specific platforms (we call them > >>> > >>> Variants), > >>>>>> e.g. just ping all Android (or iOS) users of the Application > >>>>>> > >>>>>> -Matthias > >>>>>> > >>>>>> On Wed, Aug 13, 2014 at 7:30 AM, <jas...@apps4u.com.au> wrote: > >>>>>> > >>>>>>> HI I'm wanting to add push messaging to usergrid I would like to > >>>> submit a > >>>>>>> pull request once its done but I wanted to get some input form the > >>> > >>> dev > >>>> team > >>>>>>> on my Idea as I would like to submit a pull request , > >>>>>>> > >>>>>>> The Idea I had for push messaging is a bit different to how ApiGee > >>> > >>> has > >>>>>>> implemented it I want to have notifiers but in context to a > >>>> Application so > >>>>>>> instead of having notifiers for each type of device I want to have > >>>> notifier > >>>>>>> for applications . Also the current code I have user queues to > queue > >>>> up the > >>>>>>> messages using either iron,io or beanstalk . > >>>>>>> > >>>>>>> Please let me know if this is not something that would be accepted > >>> > >>> as a > >>>>>>> pull request and if any body has any input please respond, I should > >>>> have a > >>>>>>> pull request ready within a week. > >>>>>> > >>>>>> -- > >>>>>> Matthias Wessendorf > >>>>>> > >>>>>> blog: http://matthiaswessendorf.wordpress.com/ > >>>>>> sessions: http://www.slideshare.net/mwessendorf > >>>>>> twitter: http://twitter.com/mwessendorf > >>> > >>> -- > >>> Matthias Wessendorf > >>> > >>> blog: http://matthiaswessendorf.wordpress.com/ > >>> sessions: http://www.slideshare.net/mwessendorf > >>> twitter: http://twitter.com/mwessendorf >
