I think this is look really good!
Here some thoughts, and/or possible additional use-cases
* How do we want to handle multiple devices for one user?
* How do we want to handle the other side of unified push (non-native)?
** Might just not be there yet, but want to make sure we're still thinking
the same thing :-)
** Would there be an additional abstraction above this for that?
* I'm assuming there is no good way for apps to notify you when they are
uninstalled?
** As a way of removing clutter in our tables.
* Push filtering - I would think IDM would be very good here.
** Sending to roles, groups, etc...
** When we store the device and app info what sub-system are you thinking?
*** I know you were using mongo for some of the prototyping
*** Would be possible to abstract to the IDM?
On Wed, Mar 13, 2013 at 12:58 PM, Douglas Campos <qmx(a)qmx.me> wrote:
On 13/03/2013, at 10:28, Matthias Wessendorf <matzew(a)apache.org> wrote:
> ome more APIs, for some basic (initial) functionality:
>
>
https://gist.github.com/matzew/c5fbc23bc97dfead46e1
I like the current form, but I'm sure we'll get asked about more OO(ish)
APIs, like device.send(Message) - is this on the plans?
> User/Dev enrollment can be addressed by (hopefully) reusing the
ag-security.
+1
-- qmx
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
blog:
http://in.relation.to/Bloggers/Jay