Hi Gustavo,

On Mon, Feb 28, 2011 at 10:20 AM, Gustavo Sverzut Barbieri
<barbi...@profusion.mobi> wrote:
> I've worked with expat before and it's way more complex to use and
> heavy. Sure, it will work and will handle namespace, and encoding...
> but many times you don't want or need it.
>
> the current SAX-like api I'm calling is 1 single function that
> receives a buffer and a callback, calls you back with pointers to the
> buffer you handled it. It does not consider any form of encoding, thus
> it will never break, it's up to you. It will fallback nicely on
> unhandled conditions, like entity definitions are not handled, they
> are given to you as an open tag statement. That is because MOST of
> these files are ascii and do not use these xml nasty features such as
> entities & like.

I agree with you this is a good thing to have in eina... particularly
because efreet could be based on top of this. However, I think it'd be
good if you could provide some benchmarks with libxml2 vs expat vs
eina.


regards,

Lucas De Marchi

------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to