<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 2, 2014 at 8:40 AM, Daniel Bevenius <span dir="ltr"><<a href="mailto:daniel.bevenius@gmail.com" target="_blank">daniel.bevenius@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">><span style="font-family:arial,sans-serif;font-size:13px">Not sure I get why that is not created on default. When I am not doing the create-channel, an 'application' (e.g. curl or UPS) has no location to send a >payload for the device, right?</span><div><font face="arial, sans-serif">My understanding is that the device registers not the application, which for example could be a web browser/user agent.</font></div></div></blockquote><div><br></div><div>right and the URI, returned to the 'user agent' can be stored on your 'application', like UPS.</div><div><br></div><div>I wonder why I (being a device/user-agent) explicitly have to create that channel. </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><font face="arial, sans-serif"> It will then create channels for potentially multiple applications. </font></div></div></blockquote><div><br></div><div>ok, I see that a few extra 'creates' are needed, for multiple channels. But what's the use case of a register without creating a channel? Just simply to monitor on an existing or different channel ?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><font face="arial, sans-serif">In the case of usage with the Push-API, a service worker would handle the interaction with the WebPush server and hand out channels to applications. It would also be responsible for handling the inbound notifications, and can take different actions depending on the state of the webapp (post it to an open window, store it, show notification).</font></div><span class=""><div><font face="arial, sans-serif"><br></font></div><div><span style="font-family:arial,sans-serif;font-size:13px">></span><span style="font-family:arial,sans-serif;font-size:13px">Can a device have multiple monitoring channels? (e.g. channels per topic, like #Rihanna #ZZtop #ACDC ? Can a device 'un monitor' ? </span></div></span><div><span style="font-family:arial,sans-serif;font-size:13px">I think that an application would create separate channels for topic it requires. </span></div><div><font face="arial, sans-serif">Not sure about unmonitoring. I've not see anything about that (unless I completely missed it)</font></div></div></blockquote><div><br></div><div>Not sure, but I think it might be useful to have an unmonitor, to quite the abo of some content, e.g. at some point <span style="font-family:arial,sans-serif;font-size:13px"> </span><span style="font-family:arial,sans-serif;font-size:13px">#Rihanna</span><span style="font-family:arial,sans-serif;font-size:13px"> might get boring :-) </span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Well, sue I can still 'ignore' it in my code of the service-worker, but would be nice if that guy was no longer bothered :) </span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Or am I having a misunderstanding of the concept here ? </span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><font face="arial, sans-serif"><br></font></div><div><font face="arial, sans-serif"><br></font></div><div><br></div><div><font face="arial, sans-serif"><br></font></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On 1 December 2014 at 17:49, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Hi,<div><br></div><div>after performing register, I get URIs for my channel/monitor, like:</div><div><br></div><div><br></div><div><div>register</div><div> [streamid:3] ChannelLink: webpush/7df2add5-ec4b-42a2-805f-5f8fcf8faa96/channel, MonitorLink: webpush/7df2add5-ec4b-42a2-805f-5f8fcf8faa96/monitor</div><div><br></div><div><br></div><div>I wonder why I do have to explictly create the channel?</div><div>create-channel webpush/7df2add5-ec4b-42a2-805f-5f8fcf8faa96/channel<br></div><div><br></div><div>Not sure I get why that is not created on default. When I am not doing the create-channel, an 'application' (e.g. curl or UPS) has no location to send a paylload for the device, right?</div><div><br></div><div> <br></div><div><br></div><div>Can a device have multiple monitoring channels? (e.g. channels per topic, like #Rihanna #ZZtop #ACDC ? Can a device 'un monitor' ? </div><div><br></div><div><br></div><div>Thanks :-) </div><span><font color="#888888"><div><br></div><div><br></div>-- <br><div>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div>
</font></span></div></div>
<br></div></div>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a></div>
</div></div>