AGDROID-45
by Yavuz Selim YILMAZ
Hi all,
I would like to work on https://issues.jboss.org/browse/AGDROID-45 if none of you has it in his/her agenda. Though the solution should be trivial, if you don't mind, I'd like to get my hands dirty and receive some feedback on both coding and the workflow.
Thanks and regards,
---
Yavuz Selim Yilmaz
SUNY at Buffalo
Computer Science and Engineering
PhD Candidate
10 years, 11 months
How should unified push clients handle HTTP 302?
by Karel Piwko
Hi All,
during testing OpenShift cartridge for Unified Push Server, I've realized that
if cartridge is idle, a request wakes it up and returns HTTP 302, so the
original requests is not processed. The subsequent requests is processed fine,
as expected.
I'm wondering whether we should make this transparent to use client users or
they would need to tread this on their own.
Your thoughts?
Karel
10 years, 11 months
AeroGear 1.1.0 / Push Release Pre-flight Checklist
by Douglas Campos
Heeeya!
We're getting close to AeroGear 1.1.0 / Push Release
According to our initial top-level roadmap[1], this release will be a mix
of partial items from 1.1.0 and 1.2.0 complete.
After it we'll re-sync with the additions to it, like the SimplePush
Server, Security extra features, Android Cookbook, AeroDoc, ...
For this to happen smoothly, I'd like to do a few requests:
- I'd like to ask each individual sub-lead to do a through JIRA review
so we can align all the trackers converging to the 1.1.0 release.
- I'm starting to put the release blog together[2], and would like to start
gathering a small description from each subproject to be highlighted
on it. Could you please provide a single paragraph saying about the
news and linking to your own release blog?
- The site restyle is almost done, and the plan is to ship it this week
- if you haven't had the time to nitpick and test on all your devices,
this is the perfect opportunity!
Thank y'all for helping on this last-mile!
[1]:https://github.com/aerogear/aerogear.org/blob/master/docs/scratchpad/A...
[2]:https://github.com/aerogear/aerogear.org/pull/113
--
qmx
10 years, 11 months
Inconistent website style headings
by Hylke Bons
Hi,
When implementing the new website style, I've noticed that many of the
header styles (h1, h2, etc...) are used inconsistently. This makes for a
messy looking website.
This is a big task to change all over the place by myself, so I need
your help.
So whenever you change a page in the documentation next time, please
make sure that the first header is "h1", and everything that is a
sublevel from there is "h2" up to "h4". Also, ideally we only want a
single "h1" per page and it should be at the very top.
Thanks!
Hylke
10 years, 11 months
Embedding Aerodoc Simple Push Web Client into Aerodoc Back End
by Sebastien Blanc
Hi Folks !
When we started the Aerodoc Quickstart project, the Simple Push Web Client
was part of the Aerodoc Backend project, hosted in a sub path (/client).
Once we got the code stable, we decided to move it to it's own repo :
https://github.com/aerogear/aerogear-push-quickstart-web. But I kept it
testing by copying it each time into the deployed aerodoc war.
These last days, while helping for the webinar and started using the web
client as "standalone" meaning deployed apart from the backend, I started
to face some issues that I won't elaborate here but the TL;DR : using CORS
with secured JAX-RS endpoints isn't working, be sure I will open a thread
and related JIRAs about this.
So, for now we decided to embed again the client with the backend, we've
got a working branch here :
https://github.com/sebastienblanc/aerogear-push-quickstart-backend/tree/w...
and
for the August release it seems the way to go (I will PR this branch
against master).
Once, we have resolved the remaining issues, the Client will move back to
his repo.
Any questions, feedback are welcome.
Seb
10 years, 11 months
