Re: [Webpush] Receipt subscription follow-up

[Costin Manolache <[e-mail]>]

+1 on adding a DELETE.  GCM does the same in XMPP receipts, with an ack.
One problem would be that we'll have an extra RT, since delete requires a
response frame - in XMPP it's a one-way ack.

I don't know if TCP flow control and TCP acks are enough.
How does the HTTP/2 flow control window apply to push promises ?

Another option would be to just use regular http and some json or plain
text to pull batches of receipts.

Costin

On Tue, Apr 26, 2016 at 9:21 PM Martin Thomson <[e-mail]>
wrote:

> On 27 April 2016 at 14:12, Costin Manolache <[e-mail]> wrote:
> > How does the PS know that AS can accept more receipts, and how does it
> know
> > a receipt has been accepted by the AS ?
>
> There is no explicit h2-layer acknowledgment of a push.  That all
> happens implicitly with TCP acks and maybe with flow control acks.  In
> HTTP, a server usually doesn't get to learn if its response made it
> until the client acts on the response in some way.
>
> However, in this case, can we request that the application server
> DELETE (just like the client uses DELETE to acknowledge)?
>