Re: [Webpush] Replacing Push Messages just with Topic. Why?
Martin Thomson <martin.thomson@gmail.com> Tue, 14 June 2016 13:54 UTC
Return-Path: <martin.thomson@gmail.com>
X-Original-To: webpush@ietfa.amsl.com
Delivered-To: webpush@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id A7E8612D607
for <webpush@ietfa.amsl.com>; Tue, 14 Jun 2016 06:54:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id q24CAIr2jWT3 for <webpush@ietfa.amsl.com>;
Tue, 14 Jun 2016 06:54:42 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com
[IPv6:2607:f8b0:400d:c09::234])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 2C14712B074
for <webpush@ietf.org>; Tue, 14 Jun 2016 06:54:42 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id c73so62486974qkg.2
for <webpush@ietf.org>; Tue, 14 Jun 2016 06:54:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=WqvGl3Ks58VID0qa/WkbtmdkhcC0lQtzAn+bpdLGt88=;
b=UN+fNOmk1KAiVSKxfCvsrmNBfhyGLmeug/aSKbqu3EIXxc6RFK66YRwmOoZkTBjN9Z
AJ2VwG9xqranJPni1vHM0Q6oFsEKL/B7G2xPwPbcfOfs+mrXyanS8GKPGi47oj5YeWt5
wpdEJoIgPJOl+ubZSSnM3tV+38pgDMXnwnXIC/6pvt6SDjJbMnbwr2Zaej7vZHeapSsp
jTFYWyzM/o5x8vpvd7kFfg+WvMeJE1Ge3V7WEREYITh7MIhIwbgkA4TPuuOK+a+8vzly
JTw6paDEjEK5ECiZfbaRO8WCIkaETo/gC2oX75AW/kuZug7yzkmDieNOo5K0i1fQDSVY
5OJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=WqvGl3Ks58VID0qa/WkbtmdkhcC0lQtzAn+bpdLGt88=;
b=AofCvS3iikGCrIXBmuZPiUxsgTplPqKLsJEPJ9Yrj0jId19j0EjfFuMZIUrr2rcr4+
WaKRxuhPburTZdUk4XhD9VmTEyOz4nMAXCFCVFPknHpljVnsh/83s6rRVKGQpsTN4mwJ
uTcgCghaePqeNtiKKCdmjPbNMyShm95EH86Tg6LYigG671UdoGjQvl2pzE5nwOyQvh5y
cdcFF/38VfLyq5oTrMQN1lfGDc1IIzY4bDxOSUCx3Z2vS8K/9+sBzsvj+thrhwEduPs0
GVUOgLqrC8nLElCrQUh9nXO76Q1DrjB4VOjktAcKUNpBoNtYxODuvMeX9lrmqh0V7BLt
I58Q==
X-Gm-Message-State: ALyK8tJtnDI85dUyVRcAuT2pIfYHN/5dwtf23kMJOrm8RdsY97MiX7WcFLaMqWGPxCnR4vQhi88Elca/SOGKoQ==
X-Received: by 10.55.78.16 with SMTP id c16mr8840486qkb.48.1465912481219; Tue,
14 Jun 2016 06:54:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.104.37 with HTTP; Tue, 14 Jun 2016 06:54:40 -0700 (PDT)
In-Reply-To: <CAN+BUJqkGrtMCCdFBGxoviUPW3+ipmfqNeB57K8Yab1kreBNZw@mail.gmail.com>
References: <CAN+BUJqkGrtMCCdFBGxoviUPW3+ipmfqNeB57K8Yab1kreBNZw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 14 Jun 2016 14:54:40 +0100
Message-ID: <CABkgnnX7M_BqoAmvVvwTZkJdSjKnXahA9mEkiy-YWz2LXRWNzQ@mail.gmail.com>
To: Idel Pivnitskiy <idel.pivnitskiy@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/iaElZ-dVi6kYNnX_T1_McuNl29U>
Cc: "webpush@ietf.org" <webpush@ietf.org>
Subject: Re: [Webpush] Replacing Push Messages just with Topic. Why?
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussion of potential IETF work on a web push protocol
<webpush.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webpush>,
<mailto:webpush-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/webpush/>
List-Post: <mailto:webpush@ietf.org>
List-Help: <mailto:webpush-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webpush>,
<mailto:webpush-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jun 2016 13:54:43 -0000
On 14 June 2016 at 14:25, Idel Pivnitskiy <idel.pivnitskiy@gmail.com> wrote: > Why a user can replace push messages just with topics? Why we don't allow > him to replace any message providing push message resource? Looks like it > may simplify implementation. And no need to worry if user didn't assigned a > topic to the message which he wants to replace. We had a discussion about this at our Yokohama meeting, where I presented exactly this idea. It was observed that many applications don't want to keep state about the messages that they want to replace. In order to replace based on the resource URL, they have to wait for the response from the server as well, which was also considered inconvenient. Topics are simpler to manage.
- Re: [Webpush] Replacing Push Messages just with T… Martin Thomson
- [Webpush] Replacing Push Messages just with Topic… Idel Pivnitskiy