Hi, This is a reasonable thing to do, as long as you don’t mind the AMP connections being alive all the time. For the most part, the AMP push stuff we have is for testing purposes (e.g. our client simulator can use it). One big difference between this and apple’s service (APNS) is that APNS uses a single TCP connection to transmit all pushes from all interested parties to a single device, making it (almost) infinitely more scalable than AMP.
If you’re successfully registering for AMP pushes, then it sounds like you’re doing it right. Maybe check out the following for clues: The server side: http://trac.calendarserver.org/browser/CalendarServer/trunk/calendarserver/push/amppush.py Client side example; this tool just registers for notifications / prints them to stdout: http://trac.calendarserver.org/browser/CalendarServer/trunk/calendarserver/tools/ampnotifications.py -dre > On May 27, 2014, at 5:38 AM, Atli Thorbjornsson <atlith...@gmail.com> wrote: > > Hi all, I'm trying to figure out if I can receive all caldav notifications > via AMP? I have a client that successfully registers with the calendarserver > but never gets any notifications of any changes. > > Basically I want to create something similar to the apple push notification > service that is included. I need to notify clients that are running on other > platforms so I thought I could hook up my own service via AMP. > > Am I barking up the wrong tree? > > Atli Thorbjornsson > _______________________________________________ > calendarserver-dev mailing list > calendarserver-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/calendarserver-dev _______________________________________________ calendarserver-dev mailing list calendarserver-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/calendarserver-dev
