[aerogear-dev] Imporovements to Push Server draft (Was: Some questions about the Unified Push Server...)

Matthias Wessendorf matzew at apache.org
Wed May 29 11:42:13 EDT 2013


Hi, Hylke!

nice work - comments inline


On Wed, May 29, 2013 at 5:32 PM, Hylke Bons <hbons at redhat.com> wrote:

>  Hey,
>
> Whilst reading through the AeroGear Unified Push Server draftI went ahead
> and fixed a few typos and did some a tiny bit of rephrasing where needed in
> the spec. As I was bored yesterday evening I've fixed up the infographic as
> well. :)
>
> The commit can be found here:
>
> https://github.com/hbons/aerogear.org/commit/7f348ed3ee1dab6e43d18c09dac92ef827c8fa11
>



Thanks for fixing the typos and adding some better English :))



> Sources for the infographic:
> https://github.com/hbons/aerogear-design
>

wow - I like the graphic. A few more "corrections"

1) Developers can also add "SimplePush variant"
2) How about "Mobile application (aka MobileVariantInstance), running on
the device, register themselves using a token" ?
3) I think JBoss AS backend server makes sense here - however, it can be
bloody PHP app as well :)
4) Possible to add a "cloud" to represent the different push networks (for
iOS(APNs), for Android (GCM) and SimplePush) ?


Makes sense ?




>
> (it may make sense to have a dedicated design repo in the Github
> organisation?)
>
> Let me know what you think and I'll create a pull request if it gets the
> go ahead.
>


yeah, let's have a PR (perhaps with an updated version of the image) ?


-M



>
> Thanks,
>
> Hylke
>
>
>
> On 29/05/2013 10:17, Hylke Bons wrote:
>
> Thanks! Makes sense. :)
>
> Hylke
>
> On 29/05/2013 06:49, Matthias Wessendorf wrote:
>
> Hello Hylke,
>
> 1) Admin user: This should be 'Developer', mentioned in the spec document
> you are referring to (looks like a typo)
> 2) UnifiedPush Server: Yes, that gray thing is basically the UP Server
> 3) yes, backend does not need to run on the same machine.
> --> The UP-server could be deployed in the cloud and backends (hosted
> somewhere else), can access it. That's why the UP-server has HTTP
> interfaces. So even a PHP application could send messages to it.
>
>  -Matthias
>
>
>
>
> On Tue, May 28, 2013 at 10:27 PM, Hylke Bons <hbons at redhat.com> wrote:
>
>> ...overview graphic found on
>> http://staging.aerogear.org/docs/specs/aerogear-server-push/.
>> I've annoted my questions in an image as they're worth a thousand words.
>> :)
>>
>> Thanks,
>>
>> Hylke
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
>  --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> _______________________________________________
> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
> _______________________________________________
> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130529/684709da/attachment-0001.html 


More information about the aerogear-dev mailing list