Re: [Ann] Jivan 1.0 RC 1

Arno,
You were an early xmlc developer (and architect of the earlier xmlc 
frameworks), so I'm curious why you decided to re-invent xmlc?  Of the 3 
items below, the one that stands out is performance.  To save me a lot 
of time investigating jivan, I'm curious why you just didn't propose a 
different page-manipulating engine for xmlc?  From what I can tell of 
the jivan from the Sample page, it looks pretty darn similar (setText 
and all).

thanks,
David

Arno Schatz wrote:

> Hi,
> 
> I have been working on the Jivan Project (www.jivan.org) for a while, It 
> is an open source project. Similar to XMLC it can parse HTML, lets you 
> manipulate the HTML DOM and can seialize the result. It is optimized for 
> use in web applications.
> 
> There were 3 reasons to write Jivan and not use xmlc for HTML pages:
>  - performance: Jivan is more than 3 times faster in table replication 
> (see www.jivan.org   for performance result)
>  - ease of use: Jivan doesn't compile anything and does not need to be 
> included in the build process (hence no ant taskdef neccessary)
>  - dealing with invalid HTML: Jivan leaves the HTML page as it is, 
> except those places you dynamically change. Jivan parses almost any HTML 
> without fixing (unlike xmlc). While serialisation, for all nodes (and 
> subtrees) which are not touched by the programmer, Jivan will copy the 
> coresponding HTML string from the supplied template directly to the output.
> 
> 
> Jivan uses the latest form Apache.org: Xerces-2 and nekoHTML.
> 
> Similar to xmlc, you manipulate the web-page through the standard 
> interfaces from W3C DOM for HTML.
> 
> check it out at www.jivan.org and give me some feedback,
>     Arno
> 
> 
> _______________________________________________
> XMLC mailing list
> [email protected]
> http://www.enhydra.org/mailman/listinfo.cgi/xmlc
> 
> .
> 


-- 
David H. Young
SAMBA Holdings, Inc.
Chief Technology Officer
1730 Montaño NW
Albuquerque, NM 87107
505.797.2622 x113
http://www.samba.biz