Here's an initial version:
I tried to incorporate most wishes expressed in the other thread.
Most notable things:
- Landing page with an overview of stats, most active apps, and error
- Activity table shows both registration and notification events
- Activity table is per variant, and not all activity on the server.
Unless there's a usecase to have every event for every app/variant in a
table I don't think we actually need it. The important thing is to get
to error messages easily.
Things to do/think about:
- links/entry points to the activity table
- filtering the activity table
This is just the first iteration and we will improve on this.
Let me know what you think.
Good morning, after talking with Corinne and Christos we are planning a
IRC meeting on Monday (Jun 2) 12 p.m BRT, just after our team meeting.
The goal is to discuss the offline spec, what we've been planning and
how it could help OAuth2 implementation on the client side.
If you want to join, let us know.
for  I'd like to propose we introduce a custom http-header
('aerogear-sender') to be submitted by our "clients" that perform a send in
order to show the user on the 'stats' page what client was used to submit a
'push job' to the server.
I have identified the following clients to be updated (see sub-tasks of
* AdminUI (compose a push UI part)
On our clients we can simply apply the new custom header, however that does
not work for pure invocation of our REST APIs (e.g. via cURL or if someone
did build their own sender (E.g. some company builds an internal Ruby
sender)). For that case I suggest to simply read the "user-agent" header.
Basic rule: If there is no "aerogear-sender" header present, we read the
value of the "user-agent" header.
Any thoughts ?
Now Cordova has it’s own jira project and therefore it’s own version number, but in github the plugins have their own repository. Would it make sense to move all the plugins into one central github repository and when making a release to release all of them?