Currently we have the UPS admin UI embedded into
Could the admin-ui be a separated project (repository) with its own war
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
+55 11 99703 0621
how do people feel about an batch processing endpoint:
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 ?