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

Matthias Wessendorf matzew at apache.org
Wed May 29 13:39:56 EDT 2013


On Wed, May 29, 2013 at 7:36 PM, Sebastien Blanc <scm.blanc at gmail.com>wrote:

>
>
>
> On Wed, May 29, 2013 at 7:23 PM, Matthias Wessendorf <matzew at apache.org>wrote:
>
>> Almost :)
>>
>> Hybrid would not use SimplePush :) It would use GCM (Cordova on Android)
>> or APNs (Cordova on iOS).
>>
>
> Speaking of this, shouldn't we be thinking on how we could provide a
> smooth migration for the developer who has a pure web app (using push and
> in this case in combo with SimplePush) and who wants to turn it into a
> hybrid app ? How can we manage keeping as much as possible a common base
> code ?
>  I can see here maybe some space  for tooling : like a push-migration
> forge plugin ...
>

yeah, but lets discuss that in a different thread.

Generally, using our polyfill w/ Cordova should not be a problem at all

-M




>
>> 2)
>> "Adds iOS, Android or SimplePush variant", ok ?
>>
>> 4) Let's use the SimplePush (not Simple Push)
>>
>>
>> Mozilla writes it that way as well:
>> https://wiki.mozilla.org/WebAPI/SimplePush
>>
>>
>>
>> On Wed, May 29, 2013 at 6:52 PM, Hylke Bons <hbons at redhat.com> wrote:
>>
>>>  Here's the updated graphic:
>>> https://github.com/hbons/aerogear-design/blob/master/aerogear_unified_push_server.png
>>>
>>> Hylke
>>>
>>>
>>>
>>>
>>> On 29/05/2013 16:57, Matthias Wessendorf wrote:
>>>
>>>
>>>
>>>
>>> On Wed, May 29, 2013 at 5:52 PM, Hylke Bons <hbons at redhat.com> wrote:
>>>
>>>>  On 29/05/2013 16:42, Matthias Wessendorf wrote:
>>>>
>>>>
>>>>  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" ?
>>>>
>>>>  Sure, I'll fix that.
>>>>
>>>>
>>>  cool
>>>
>>>
>>>>
>>>>    3) I think JBoss AS backend server makes sense here - however, it
>>>> can be bloody PHP app as well :)
>>>>
>>>>  True, I think this is a minor detail and it's better to mention that
>>>> as an annotation to the image? Something like "This graphic shows the
>>>> interactions between Push Applications and the Unified Push Server using a
>>>> JBoss backend as an example.".
>>>>
>>>
>>>
>>>  yep
>>>
>>>
>>>>
>>>>
>>>>
>>>>   4) Possible to add a "cloud" to represent the different push
>>>> networks (for iOS(APNs), for Android (GCM) and SimplePush) ?
>>>>
>>>>    I don't draw clouds. ;)
>>>>
>>>
>>>  LOL
>>>
>>>
>>>>  Are you refering to the word "PushNetworks"? I think it does make
>>>> sense to have an extra step in the graphic there, but don't think it should
>>>> be a cloud. :)
>>>>
>>>
>>>  Yeah, I was talking about the different PushNetworks, involved. Not
>>> sure if it needs to be a "cloud". But they are considered cloud services :)
>>> Feel free to draw something else :)
>>>
>>>
>>>  Thanks for the efforts!
>>>
>>>
>>>
>>>
>>>
>>>
>>>>
>>>> Thanks,
>>>>
>>>> Hylke
>>>>
>>>>
>>>>
>>>>  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
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://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/e65eea8a/attachment-0001.html 


More information about the aerogear-dev mailing list