Re: [Json] draft-williams-json-text-sequence-00

Phillip Hallam-Baker <hallam@gmail.com> Sun, 16 March 2014 12:01 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 765E11A02DD for <json@ietfa.amsl.com>; Sun, 16 Mar 2014 05:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 RcyLku5lInZI for <json@ietfa.amsl.com>; Sun, 16 Mar 2014 05:01:13 -0700 (PDT)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) by ietfa.amsl.com (Postfix) with ESMTP id D78B11A0104 for <json@ietf.org>; Sun, 16 Mar 2014 05:01:12 -0700 (PDT)
Received: by mail-lb0-f169.google.com with SMTP id q8so3010967lbi.0 for <json@ietf.org>; Sun, 16 Mar 2014 05:01:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mZthOG5D7MCizEh9DQiTytVgYX7ayQ/J8ZB8pLcwitI=; b=emPgEe7NXfuuY72rY2mxlimkr52XHdhuyUlKa6vThnH32/LFCCPTspyFXwDbjdxJ0T sZg8HEL7fP8D1P0w950l7+J/yFP5dWqkWiZI6eqlNcuStT7nG5RuT5wUhxoyWxWILzX5 GH/24LuYONRmHYut+xYsqtF3bLOGgDa7P1hbPbPRq3WTrk7OMjAdZ3hLTStoaAFQ1ZB0 +o0iPJgO1apQn3TsyKAkdSEucI0UjZKLQrCfly/K23iY8sLyXBQIv1OyZ/GF29l7b5cX KLCw8Fl7hb9vkVqeH7sslfZW2Ivaso6rgVkdZMpaJVkNU5yov70hENoyhVN2tbOf/Y4y hHWA==
MIME-Version: 1.0
X-Received: by 10.152.2.225 with SMTP id 1mr965271lax.37.1394971264642; Sun, 16 Mar 2014 05:01:04 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Sun, 16 Mar 2014 05:01:04 -0700 (PDT)
In-Reply-To: <CAK3OfOhOjb+ZubpeMuifbkUybR9=NefXRRYvQK8y_zTfv4WpPQ@mail.gmail.com>
References: <CAK3OfOg7Ly=unmjJY2E34LZT1DyqZ9VFUs4gtNNEiMJGA9cQKA@mail.gmail.com> <20140315194123.GG24343@mercury.ccil.org> <CAMm+LwiPrm+yx-oQwpKU2fLh6OsNsQZMyidnXwMHOryptxppZw@mail.gmail.com> <CAK3OfOhOjb+ZubpeMuifbkUybR9=NefXRRYvQK8y_zTfv4WpPQ@mail.gmail.com>
Date: Sun, 16 Mar 2014 08:01:04 -0400
Message-ID: <CAMm+LwgFFyNtNtV9V87DaO46cEKeJwG7EGmywE8=LbiL5g7HzA@mail.gmail.com>
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Nico Williams <nico@cryptonector.com>
Content-Type: multipart/alternative; boundary="089e013c61a0b3754704f4b80e2a"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/-xDx4Ikh8CBTv_LBiPsoRhgzy7Q
Cc: John Cowan <cowan@mercury.ccil.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] draft-williams-json-text-sequence-00
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Mar 2014 12:01:15 -0000

On Sun, Mar 16, 2014 at 3:52 AM, Nico Williams <nico@cryptonector.com>wrote:

> On Sat, Mar 15, 2014 at 3:53 PM, Phillip Hallam-Baker <hallam@gmail.com>
> wrote:
> > I am thinking that the best way to show off JSON sequence would be to
> update
> > this draft from '96
> >
> > http://www.w3.org/TR/WD-logfile.html
> >
> > It is a widely used format but it has problems, every entry has to
> specify
> > entries for precisely the set of data advertised at the start.
> >
> > I am thinking of redoing the spec in JSON using the same tags to identify
> > the data elements.
>
> Speaking of which... what is the best way to longpoll (tail -f) a log
> file over HTTP?
>

Make a HEAD request to find out the Content-Length, then to poll for
updates after that point, use the range parameter.

But a Web Service to fetch the info would make matters a lot easier.

-- 
Website: http://hallambaker.com/