ups admin ui
by Leonardo Rossetti
Hello,
Currently we have the UPS admin UI embedded into
aerogear-unifiedpush-server project/repository.
Could the admin-ui be a separated project (repository) with its own war
file?
While it may increase release process complexity (a new project
dependency), I think it brings some benefits to the table, such as having a
development cycle of this own, easier to write automated tests and easier
to attract contributors from the javascript community (since we would be
using common javascript tools to build it).
WDYT?
--
Leonardo Rossetti
lrossett(a)redhat.com
+55 11 99703 0621
4 years, 4 months
Push - Batch processing endpoint ?
by Matthias Wessendorf
Hi,
how do people feel about an batch processing endpoint:
https://github.com/aerogear/aerogear-unifiedpush-server/pull/794
Use-case:
If you have a list of different users (via different alias), and want to
send them a personalized message (e.g. "Hello $alias, how are things?"),
CURRENTLY you'd have to iterate through that list and send a push request
for _each_ alias/message pair. Which results in lot's of overhead, and
lot's of http requests;
Now, using this new batch endpoint, allows you do iterate through the list,
create the actual message, put it to a collection, and after the iteration,
you send one HTTP request, containing the message collection.
This results in ONE http request, which it may contain 100's of different
messages, for the given Push-Application, instead of 100's of HTTP requests.
Any thoughts ?
-Matthias
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
4 years, 5 months
