Re: [apps-discuss] Fwd: Media type for lists of changed URIs?

Jan Algermissen <jan.algermissen@nordsc.com> Wed, 08 January 2014 15:10 UTC

Return-Path: <jan.algermissen@nordsc.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF411AE429 for <apps-discuss@ietfa.amsl.com>; Wed, 8 Jan 2014 07:10:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level:
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=no
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 8Nl4q6TEqC54 for <apps-discuss@ietfa.amsl.com>; Wed, 8 Jan 2014 07:10:38 -0800 (PST)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by ietfa.amsl.com (Postfix) with ESMTP id B92AB1AD8D5 for <apps-discuss@ietf.org>; Wed, 8 Jan 2014 07:10:37 -0800 (PST)
Received: from [10.90.143.216] ([87.253.171.202]) by mrelayeu.kundenserver.de (node=mrbap4) with ESMTP (Nemesis) id 0MZDyO-1VfwVy3ha0-00KzQz; Wed, 08 Jan 2014 16:10:27 +0100
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jan Algermissen <jan.algermissen@nordsc.com>
In-Reply-To: <CAKioOquabW6RpPoAeheVSL0zOv3K6P-eyBB0FcyHvS6PpJ3-HQ@mail.gmail.com>
Date: Wed, 08 Jan 2014 16:10:26 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5DC99287-9CB0-48B6-B237-CFDEAF8BCB8E@nordsc.com>
References: <A4A8D5B5-73D7-4F4C-968A-D23337DF4FA2@nordsc.com> <CAKioOqsz_GPu3LmZjnv6MBWx9ENHEu8nzSDEsN=4WCpZeb_YLg@mail.gmail.com> <CAKioOquabW6RpPoAeheVSL0zOv3K6P-eyBB0FcyHvS6PpJ3-HQ@mail.gmail.com>
To: darrel@tavis.ca
X-Mailer: Apple Mail (2.1510)
X-Provags-ID: V02:K0:SNx5fJ5htnhyylFlPykTPDf2sZOlo09uH/i6N8leW4Y GTMTJ0abytQeGNbZNJU6hOUoJLIkeNHp1txCamgaC0T7hpIxy+ 4woFF7e9p6CqSF7tooZ1K0FvFSC69MsH5XJYcDqguqIbhepOyS VaysKOwIy8pKf9mzsMNLqmZBWB4DQkedaiDVgP8bMZ+Lx9qoPA 85HKptyy9iplVy0y/EecMbNKNLLeUv0JkVtTnsZV+2CYAn7d/R +MU2kWJlGkE3HbfgJeNLzO2I+NBYlwi+NgPWIF1zg3e/9u2NNz lsM/wqqvQInAp21iurgXiqoc9YOBzVWebMVQyGjMz4ZxW4hsoe ZgJxBhkG9WBzKSSOtTchoeqHQnZXp8gBpO2olCzeuPBS+ZITxM M57m5nOAxEu5Q==
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Fwd: Media type for lists of changed URIs?
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss/>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 15:10:40 -0000

On 08.01.2014, at 16:08, Darrel Miller <darrel.miller@gmail.com> wrote:

> Argggh gmail.  Forgot to cc the list.

Well then, here's my reply again :-)

> 
> 
> ---------- Forwarded message ----------
> From: Darrel Miller <darrel.miller@gmail.com>
> 
> Could you instead define a link relation like rel="changed" and then
> return text/uri-list ?

Yes, exactly where I am at.

However, I'd like to remove the burdon of timing issues from the "protocol" and instead use linked paged (rel=prev-archive) for clients to process backwards until their last remembered timestamp.

Hence, I'd need something like

timestamp uri
timestamp uri

and this is where I wrote the last email :-)

Jan



> 
> Darrel
> 
> On Wed, Jan 8, 2014 at 9:46 AM, Jan Algermissen
> <jan.algermissen@nordsc.com> wrote:
>> Hi all,
>> 
>> I am about to work on a media type for transferring lists of URIs of resource that have changed to an 'observer' of a collection of resources.
>> 
>> It just occurred to me that something like that might already exist in the context of cache invalidation protocols.?
>> 
>> Jan
>> 
>> 
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss