[aerogear-dev] Unified Push Server integration capabilities

[Wolfgang]

Hello dear aerogear dev team,

a couple of weeks ago we had to integrate a PushServer for iOS and Android
into our solution. We used the UPS out-of-the-box for a first prototype to
figure out better the capabilities and to be able to better define the
requirements in regards to push. So far we are very excited about the
product!

The drawback is that some piece of information like devices, users, apps as
are represented in another system (i.e. MongoDB) or capabilities like
authorization/authentication are already present. Thus there is some
redundancy and overhead and the UPS is a little bit alien in regards to the
rest of the existing architecture/infrastructure. This has pre and cons -- I
know ...

I thought that maybe a "simple"/exchangable mechanisms (e.g. persistence
layer) of defined integration interfaces and mechanisms would be great in
order to be able to better integrate the UPS in existing or already
constrained system environments. This might also help in regards to
scalability and flexibility of the existing design/architecture.

Wondered if that would make sense in your opinion ... ?

~Wolfgang 



--
View this message in context: http://aerogear-dev.1069024.n5.nabble.com/Unified-Push-Server-integration-capabilities-tp5755.html
Sent from the aerogear-dev mailing list archive at Nabble.com.