Re: draft-freed-sieve-in-xml status?

Ned Freed <ned.freed@mrochek.com> Sun, 14 December 2008 22:03 UTC

Return-Path: <owner-ietf-mta-filters@mail.imc.org>
X-Original-To: ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com
Delivered-To: ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD9583A67F1 for <ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com>; Sun, 14 Dec 2008 14:03:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level:
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ubT2dPuPjOv for <ietfarch-sieve-archive-Aet6aiqu@core3.amsl.com>; Sun, 14 Dec 2008 14:03:36 -0800 (PST)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 9E1F63A679F for <sieve-archive-Aet6aiqu@ietf.org>; Sun, 14 Dec 2008 14:03:35 -0800 (PST)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id mBELwHUq086884 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 14 Dec 2008 14:58:17 -0700 (MST) (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id mBELwHME086883; Sun, 14 Dec 2008 14:58:17 -0700 (MST) (envelope-from owner-ietf-mta-filters@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id mBELwGEZ086876 for <ietf-mta-filters@imc.org>; Sun, 14 Dec 2008 14:58:16 -0700 (MST) (envelope-from ned.freed@mrochek.com)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01N3333OJ1C000SUCW@mauve.mrochek.com> for ietf-mta-filters@imc.org; Sun, 14 Dec 2008 13:58:14 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01N31HJ3ZB0G00SE3A@mauve.mrochek.com>; Sun, 14 Dec 2008 13:58:11 -0800 (PST)
Date: Sun, 14 Dec 2008 13:56:15 -0800
From: Ned Freed <ned.freed@mrochek.com>
Subject: Re: draft-freed-sieve-in-xml status?
In-reply-to: "Your message dated Sun, 14 Dec 2008 20:39:54 +0000" <f470f68e0812141239y1651d6e3k3ced40f5f307796@mail.gmail.com>
To: Robert Burrell Donkin <robertburrelldonkin@gmail.com>
Cc: Ned Freed <ned.freed@mrochek.com>, ietf-mta-filters@imc.org
Message-id: <01N3333MY6PE00SE3A@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset="ISO-8859-1"
Content-transfer-encoding: 7bit
References: <f470f68e0812041225x318bfdccg1bf9201b53ce8c2e@mail.gmail.com> <493E908E.70504@isode.com> <f470f68e0812090956j56c29f17s77fc554adaab1350@mail.gmail.com> <f470f68e0812140341i704ba137qa04c69db2951c8ab@mail.gmail.com> <01N32UZZ0N8I00SE3A@mauve.mrochek.com> <f470f68e0812141239y1651d6e3k3ced40f5f307796@mail.gmail.com>
Sender: owner-ietf-mta-filters@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-mta-filters/mail-archive/>
List-ID: <ietf-mta-filters.imc.org>
List-Unsubscribe: <mailto:ietf-mta-filters-request@imc.org?body=unsubscribe>


> On Sun, Dec 14, 2008 at 6:02 PM, Ned Freed <ned.freed@mrochek.com> wrote:
> >> the standard talks a lot about graphical user interfaces. i'd be
> >> interested to learn how it's been implemented.
> >
> > We're using an variant of what's in the draft (an earlier version) in our web
> > client. The details are rather complex, but basically what happens is that the
> > client uses the alternate representation in order to avoid having to parse and
> > otherwise deal with Sieve syntax.

> yes - sieve parsing is probably too difficult for web applications

Well, I'm not sure I'd go that far, although the whole Javascript environment
is such a nightware you may well be right.

But regardless, the point is why force people to implement another parser in a
hugely overconstained environment when they don't need to?

				Ned