[Aerogear-users] [aerogear-dev] UPS Device Registration Endpoints

[Matthias Wessendorf]

that's cool stuff!

-Matthias

On Tue, May 31, 2016 at 8:07 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> Thanks for the info guys.
>
> Also i just released the 0.1.0 version of this
> https://www.npmjs.com/package/unifiedpush-registration-client
>
> a client for doing device registration.
>
> Currently implemented is register and unregister.  i'm working on getting
> the "importer" working for the next release.
>
>
>
> On Sat, May 28, 2016 at 12:50 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>>
>>
>> On Fri, May 27, 2016 at 10:10 PM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>>
>>>
>>> Envoyé de mon iPhone
>>>
>>> Le 27 mai 2016 à 21:56, Luke Holmquist <lholmqui at redhat.com> a écrit :
>>>
>>> thats right folks, i'm asking this question on a Friday before a Holiday
>>> weekend(US) at 3:52(est)
>>>
>>>
>>> i've started to implement the Device registration endpoints in node and
>>> was just wondering what the id is here in this header
>>>
>>>
>>> -v -H "Accept: application/json" -H "Content-type: application/json" -H "aerogear-push-id: someid"
>>>
>>>
>>> is it something specific, or just a random number/alpha-numeric thingy
>>>
>>>
>>> here is the doc link for reference:
>>> https://aerogear.org/docs/specs/aerogear-unifiedpush-rest/#246535932
>>>
>>> Let's wait for Matzew to confirm but I think you can ignore it. Looks
>>> like a left over from our first analytics implementation , we use now a
>>> separate endpoint (the PUT) and pass this ID as a path parameter.
>>> We probably need to clean up the javadoc
>>>
>>
>> correct, doc error.
>>
>> the thing is only relevant here:
>>
>> https://github.com/aerogear/aerogear-unifiedpush-server/blob/252c3a979cf05b69f061f7ffa6d3dcc8826c7b51/jaxrs/src/main/java/org/jboss/aerogear/unifiedpush/rest/registry/installations/InstallationRegistrationEndpoint.java#L203
>>
>>
>>
>>>
>>>
>>>
>>> I've also decided to create this as a separate module instead of
>>> including it in the node admin client here:
>>> https://github.com/bucharest-gold/unifiedpush-admin-client
>>> mostly becuase these registration endpoints don't needed to be KC
>>> authenticated.
>>>
>>> even if they were KC managed, they would be different (E.g. just
>> bearer-only), since there is no relationship to the actual mgmt of the
>> server.
>>
>> +1 on separating these two things
>>
>> -M
>>
>>
>>
>>>   and they could also be used on a IOT device or something that runs
>>> node that has webpush/simplePush or some new crazy protocol.
>>>
>>> Make sense , I like that
>>>
>>>
>>>
>>> -Luke
>>>
>>> _______________________________________________
>>> Aerogear-users mailing list
>>> Aerogear-users at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>>
>>>
>>> _______________________________________________
>>> Aerogear-users mailing list
>>> Aerogear-users at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>>
>>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> 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/
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160601/7806e6b3/attachment.html