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

[Matthias Wessendorf]

Oh, one more thing :)

SimplePush (JavaScript) API was developed for the FirefoxOS, and the
(Firefox) desktop browser.
The SimplePush Server/Protocol is used as the "Push Network" for
devices/browsers that support the SimplePush API.

Example:
Once Mozilla launches FirefoxOS (w/SimplePush), some "SimplePush server
implementation", deployed somewhere in the cloud (transparent to the FFOS
device), will be used as the "Push Network" for the FFOS device.

I guess, that explains why I do prefer "SimplePush" for variant and
PushNetwork.

But I am not a native speaker, so I see a room for confusion here :-)

PS: The SimplePush Server would be the same as the APNs server (but there
is no public spec for that, so we could not write our own APNs - not sure
that now makes sense

-Matthias


On Thu, May 30, 2013 at 12:28 PM, Matthias Wessendorf <matzew at apache.org>wrote:

> SimplePush was invented for FireFoxOS.
>
> But... we extend to all browsers, w/ out polyfill...
>
> Web could be used, but I prefer SimplePush.
> However, not that picky, nor interested to fight for it, over countless
> mails :-)
>
> So, feel free to use Web :-) I guess I don't have too strong ferlings
> against "web"
>
> -Matthias
>
>
> On Thursday, May 30, 2013, Hylke Bons wrote:
>
>>  Is it a "platform"? I don't see that anywhere on the Mozilla SimplePush
>> wiki page...
>>
>> Anyway, using that term there feels very out of place. Developers don't
>> create applications for "SimplePush", they create apps for iOS, Android or
>> the web. It makes much more sense from the end user point of view (this was
>> slightly confusing to me on the home page as well, where the platforms are
>> listed). It also prevents potential confusion where we have to deal with
>> both Push Networks and Mobile Variants in the admin UI. I strongly
>> recommend keeping these strictly separated (unless I'm seeing something
>> obviously wrong, please let me know).
>>
>> Thanks,
>>
>> Hylke
>>
>>
>>
>> On 30/05/2013 10:32, Matthias Wessendorf wrote:
>>
>> SimplePush: platform & network :-)
>>
>>
>>
>> On Thursday, May 30, 2013, Hylke Bons wrote:
>>
>>  On 29/05/2013 18:23, Matthias Wessendorf wrote:
>>
>> Almost :)
>>
>>  Hybrid would not use SimplePush :) It would use GCM (Cordova on
>> Android) or APNs (Cordova on iOS).
>>
>>  2)
>> "Adds iOS, Android or SimplePush variant", ok ?
>>
>>  4) Let's use the SimplePush (not Simple Push)
>>
>>
>> Yes, my bad on the typo.
>>
>> Should we mention the name of the Push Network name there though?
>> "iOS" and "Android" are platform names, but SimplePush is a Push Network
>> name.
>> This is why I went with "(Hybrid) Web" to keep things consistent.
>>
>> Hylke
>>
>>
>>  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,
>>
>> _______________________________________________
>> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://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
>



-- 
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/20130530/dc67d4f2/attachment.html