Mailing-List: contact abdera-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: abdera-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of jasnell@gmail.com designates
 66.249.82.226 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding;
        b=FWkfGmUa1VmclYZ6dHIqvrd6ExfStXDZ5/gqyzT19dmIBq2uY2GyNR+P2QajOpIVAjL3mc4izVbVGS+9pBeUEIe9BOdpDuFlnT6PbGfSpgcb3K0pag9UWD8Sy0YkA+LcCB0SBPyjnKna+hsU/G5nFH4wVwbukY4SNyK8z1G9BKY=
Message-ID: <4535A45F.2060509@gmail.com>
Date: Tue, 17 Oct 2006 20:49:51 -0700
From: James M Snell <jasnell@gmail.com>
User-Agent: Thunderbird 1.5.0.7 (X11/20060909)
MIME-Version: 1.0
To: abdera-dev@incubator.apache.org
Subject: Axiom
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

So we've been using Axiom for a while now and I think we all agree that
there are definite pros and cons.  What I'm wondering at this point is
whether or not we commit to using it long term.

I've been going through the code a bit this week trying to get an idea
of what it would take to build an impl of the core API directly on top
of StAX while preserving the incremental parsing model and xml infoset.
 It should only take a couple of weeks to do and would likely duplicate
much of the function currently in the Axiom linked-list (llom) impl but
it would also give us some freedoms to do more interesting things with
extensions, a streaming Atom parser and writer API and a jsp taglib I've
been thinking about for building out Atom documents using JSP.

At this point, so long as we maintain the incremental parse model,
preserve the lightweight memory footprint, and can still support xml
sigs and encryption, then I'm fine with moving away from Axiom.  Like I
said, I could likely have something implemented in about two weeks.

Thoughts?

- James