AeroGear Crypto Java 0.1.2 released
by Bruno Oliveira
Good morning, just to let you know we released today the bits for digital signatures and some bug fixes.
Have a happy new year sweet hearts.
--
abstractj
2 years, 7 months
Chrome Push Messages
by Lucas Holmquist
Hello,
now that the 1.0.0-final is pretty much out for the UnifiedPush Server, i’m starting to look at the new API that Chrome apps use for sending push notifications.
the TL;DR of it is, it’s basically the same as Android now.( no more refresh tokens and access tokens and such )
So the question is, do we need to have a deprecation period on what is currently there?
The v1 of the chrome pushMessaging api has become legacy and it is recommended to use the new stuff. https://developer.chrome.com/apps/cloudMessagingV1
While i have looked to deeply, it’s possible we can use the same “Variant” structure for Chrome Apps, Since they will be using the same Network
wdyt?
-Luke
9 years, 11 months
[POC] Unified Geo Server
by Sebastien Blanc
Hi all,
I have been working on a POC around geolocation. Like we discussed in
another thread, we decided not to have a "deep" integration with the Push
server but instead a separate component / microservice. Well the POC is
more a miniservice ;)
So, the idea is to have a server to which devices can register by providing
their positions. On the other side, the server provide an endpoint to make
spatial queries, like give me all the installations within a radius of 10
km around this lat/ltg.
Thanks to Forge, I created/scaffolded a really simple server providing the
registration endpoint and the search endpoint.
I tried to make a decent readme that will give you more details :
https://github.com/sebastienblanc/unified-geo-server
And as usual, I made a little screencast showing all that in action ;)
https://www.youtube.com/watch?v=R-qdLJh4EWQ
Please remember this is a POC, so the security is almost inexistant, the
console is awful ;)
What about the Client SDKs ?
If we reach some kind of consensus arounf the concept of Unfied Geo Server
we can start building the Client SDKs / POCs , they will be quite simple :
retrieve geolocation and register to the geo endpoint.
Sebi
10 years
UPS : How to get notified when an installation is deleted/updated
by Vivek Pandey
Hello UPS team,
Hope you had a wonderful Christmas!!
I am using UPS 1.0.2 (on postgres/wildfly 8.1) and wanted to understand the
best strategy to sync deletions of installation in UPS to my own db.
My current implementation stores the push token in my own db and registers
them to UPS periodically. However, currently I do not have any strategy to
sync deletions to my own db.
Does UPS publish deletion events? Or there is any bulk query mechanism to
fetch a paginated list of active installations?
Thanks,
Vivek
This message may contain privileged and confidential information and is solely for the use of intended recipient. The views expressed in this email are those of the sender and not of Pine Labs. The recipient should check this email and attachments for the presence of viruses / malwares etc. Pine Labs accepts no liability for any damage caused by any virus transmitted by this email. Pine Labs may monitor and record all emails.
10 years
Aerogear.org redesign
by Andres Galante
Hi!
I don't think there is much more I can do on the website by my own. I'll need your help to:
- Write text and correct typos. There is text to write on Homepage, Modules (add more text for each module) and Guides, you'll notice the Lorem ipsum :)
- Review the structure for Downloads, Guides and Specs
- What logos to put on the homepage footer
- Review styles and design. Did I forget to change anything that was requested?
We can discuss this in january when everyone is back. For the ones that are around: Happy holidays :)
Thanks!
Andrés
10 years
AeroGear.org - a first thought on changing our roadmap docs
by Matthias Wessendorf
Hi team,
while thinking about restructuring our roadmaps, I was wondering about our
existing roadmaps on [1]. Overall I'd like to have the AG roadmaps more
feature driven, but that requires some more thoughts/changes?
However, here is what I am wondering about...
Most of our roadmaps we link to from [1], are really just pointing to
different JIRAs.
Let's take one example, UPS:
https://aerogear.org/docs/planning/roadmaps/UnifiedPush/
Basically all info on the above page is present in JIRA (including the
'archived' roadmap of older releases). Since JIRA should be the central
tool for planing releases, features and future versions, I think that our
roadmap docs are not adding too much value, since they repeat info that is
available on a different place (JIRA).
Also, maintaining the roadmaps is tedious: You make a change on the actual
JIRA (e.g. move the date of a release or add a new feature). To keep the
roadmap up-to-date, you put the same info on the roadmap doc and send a PR.
Can we remove these roadmap docs?
For UPS that would mean, that the link on [1] would go against:
https://issues.jboss.org/browse/AGPUSH?selectedTab=com.atlassian.jira.jir...
instead of here:
https://aerogear.org/docs/planning/roadmaps/UnifiedPush/
-Matthias
[1] https://aerogear.org/docs/planning/
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
10 years
Pre-release announcement of iOS libraries
by Christos Vasilakis
Hi AeroGear community,
we are happy to announce a pre-release of our various iOS libraries. Here are few of new features introduced in each respective list:
- aerogear-ios-jsonsz (new)
A newly introduced library which will take care the cumbersome plumbing required when performing JSON serialisation back and forth from your Swift object model. For an example usage of the library together with our http-lib check our Buddies cookbook example.
- aerogear-ios-http
We added the ability to perform basic/digest authentication when performing REST Requests. Check out our Authentication cookbook example, for an example usage of the API but remember to prefer HTTPS over plain HTTP when performing authentication of this type.
- aerogear-ios-oauth2
Continuing the development of our OAuth2 library, OpenID Connect support was added to the library in the form of a ‘login’ request. Checkout out our ‘SharedShoot’ cookbook example that login's to KeyCloak using OpenID connect for an example usage.
- aerogear-ios-httpstub
Stubbed responses from the local file system can be used instead of coding them in your code. This will make easier to stub responses, especially big ones and be much ‘closer’ to the reality. Check out our tests for an example usage.
Last, this release introduces Cocoapod support for our libraries. Although Cocoapods hasn’t yet officially support ‘Swift’ that is planned for the next 0.36 release, a branch on the project is working on it and already libraries starting to adopt. Just make sure to include a Gemfile in your project pointing to that cocoapods branch (see here for more detailed instructions) and in your Podfile include the desired library. For example usage, see our cookbook repository where all of our demos have been converted.
So, give the libraries and demos a spin and let us know what you think. If no bad things heard we are planning to tag and officially release 2.1 this Friday.
Have fun!
Corinne & Christos
10 years
[Canceled] - AeroGear team meeting
by Bruno Oliveira
Good morning, due to holidays and the low number of attendees. All the meetings are canceled until next year.
If you have questions, let us know.
—
abstractj
PGP: 0x84DC9914
10 years, 1 month
