abdera-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James M Snell <jasn...@gmail.com>
Subject Re: InputStreams and contentAsXHTML
Date Thu, 18 Oct 2007 17:23:34 GMT
Look in FOMEntry in the parser module.  There are two setContent methods
that take inputstream.  The method would need to key off what kind of
content the user is setting; media content (anything other than xml,
text, html or xhtml) needs to be base64 encoded as it is now.  We are
fairly limited by the capabilities of Axiom.  I don't have the time to
look at this right now so I'd definitely encourage y'all to take a look
at submit a patch.

- James

Chris Berry wrote:
> That would be awesome.
> It will provide a significant bump in performance.
> We may look at doing this work.
> Can you point me at the right place to start.
> We would likely patch 0.3.
> Thanks,
> -- Chris
> On Oct 18, 2007, at 10:27 AM, James M Snell wrote:
>> This currently is not possible.  There are setContent(...) methods that
>> take an InputStream parameter, but they automatically convert the
>> content to Base64.  It should be fairly simple to add another option to
>> allow inputstream to be treated as Content.Type.XML.
>> - James
>> Chris Berry wrote:
>>> Greetings,
>>> I don't think this is currently possible but I'd like to check??
>>> We are building an "Atom Store" and our content is just a XML file.
>>> And for performance reasons it would make sense  (for GETs at least) to
>>> simply pass along an InputStream
>>> Can we do this without using Media content??
>>> I'm fuzzy on how all of this fits together... (so I apologize if this is
>>> a dumb question)
>>> Basically I just want to stream XML as the content, and have it show up
>>> in the Client as XML within a <content><div>...</div></content>
>>> Thanks,
>>> -- Chris
>>> S'all good  ---   chriswberry at gmail dot com
> S'all good  ---   chriswberry at gmail dot com

View raw message