IETF Logo Mail Archive

Re: Basic ietf process question ...

Mark Nottingham <mnot@mnot.net> Sat, 04 August 2012 17:01 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9D5A21F87AD; Sat, 4 Aug 2012 10:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level:
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ssg+UBU6fHyL; Sat, 4 Aug 2012 10:01:49 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8C321F8535; Sat, 4 Aug 2012 10:01:49 -0700 (PDT)
Received: from [10.130.10.92] (unknown [166.147.79.205]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id A554C22DD6D; Sat, 4 Aug 2012 13:01:42 -0400 (EDT)
References: <20120802055556.1356.17133.idtracker@ietfa.amsl.com> <CALaySJK6RE1pnk0RJZjpU8jHb9KKb3zOjGc5NqTcVyb7kTBOyw@mail.gmail.com> <CAL0qLwZaoVDtt_8o1Qr5NqG-rBk6jkAMMVT+jUUoiD2rhEvmuw@mail.gmail.com> <501AA9DF.6010208@raszuk.net> <EDC652A26FB23C4EB6384A4584434A0407E24713@307622ANEX5.global.avaya.com> <501AB4F5.7030205@raszuk.net> <501AC2C7.6040707@gmail.com> <270DDF46-AA04-49C0-B54C-35FD0AE0350F@mnot.net> <01OIMHY7BVKK0006TF@mauve.mrochek.com> <8D242074-DA5B-4C31-807D-79116517A64D@mnot.net> <01OIMJ1NAB5W0006TF@mauve.mrochek.com> <1D580354-3D3D-424B-8DE8-C5C436E8B14D@mnot.net> <CABkgnnXRu6c7RpJQoMEL8zW_=6ySM_-1Uato2GubnWtgEd=H8A@mail.gmail.com>
In-Reply-To: <CABkgnnXRu6c7RpJQoMEL8zW_=6ySM_-1Uato2GubnWtgEd=H8A@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="us-ascii"
Message-Id: <620454C2-9023-4364-9C04-97B2058D2D36@mnot.net>
X-Mailer: iPhone Mail (9B206)
From: Mark Nottingham <mnot@mnot.net>
Subject: Re: Basic ietf process question ...
Date: Sat, 04 Aug 2012 12:01:41 -0500
To: Martin Thomson <martin.thomson@gmail.com>
Cc: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>, "opsawg@ietf.org" <opsawg@ietf.org>, Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Aug 2012 17:01:50 -0000

Probably digressing here (from our previous digression), but I find a hybrid API best. E.g., the python pulldom API, which is event driven until you find a node you're interested in, whereupon it can give you an object. 

Should be even easier with json, since it can just give back a data structure. 

Sent from my iPhone

On 04/08/2012, at 11:26 AM, Martin Thomson <martin.thomson@gmail.com> wrote:

> On 4 August 2012 08:52, Mark Nottingham <mnot@mnot.net> wrote:
>>> The other interesting case is where large amounts of data arrive in a stream.
>>> SAX and SAX-like libraries makes this easy to implement with XML. I hope
>>> there's an equivalent for Json; if not there needs to be.
>> 
>> Funny you mention that, I was just looking into that yesterday.
>> 
>> This seems to be in the front running:
>>  http://lloyd.github.com/yajl/
> 
> The conclusion that I reached on this subject was that both XML and
> JSON are poorly suited to streaming use cases for large datasets.  Try
> implementing XMPP "framing" some time and tell me afterwards how much
> you love SAX.
> 
> I prefer CSV or lots of small objects.

v2.23.0 | Report a Bug | By Email