Subject: Re: [Webpush] New Version Notification for draft-begen-webpush-dash-reqs-00.txt

From: "Ali C. Begen (abegen)" <[email-masked]>
Date: Fri, 31 Oct 2014 16:10:15 +0000

On Oct 31, 2014 5:59 PM, Martin Thomson <[email-masked]> wrote:
>
> On 30 October 2014 16:58, Ali C. Begen (abegen) <[email-masked]> wrote:
> > A lightweight messaging plane between the servers (and possibly other devices on the network) and streaming clients seems also quite desirable to solve a number of issues in existing deployments.
>
> If you already have a connection to the server, is there any reason
> you couldn't use HTTP to exchange these messages?

These messages won't necessarily come from the same server. It could be an analytics server Or another network element.

>
> Web Push is intended to provide a lightweight substitute for constant
> connectivity. This is intended to ensure availability for devices that
> need to conserve scarce resources, like a phone needs to conserve
> power for its radio.

Yes I get that part and that is one of the things that make it attractive for me.

>
> Sending messages over Web Push when the target of those requests is
> already connected to you is not appropriate.  Performance worse than
> sending packets directly, and it is a far more expensive method of
> exchanging data.

Understood but as I said the messages could be coming from various entities.