You could probably reduce the size of the parser with a custom build,
and there are a few classes in the JiBX runtime jar that aren't really
needed for most purposes. I doubt you could get it down to 30 KB without
some significant changes, though.
I *have* made choices in favor of speed wherever I thought it would be
an issue. Some of those choices were probably wrong - for instance, I
special-cased a number of different data types in the unmarshalling
which, in retrospect, were not worth the effort. I'll reverse some of
these in the 2.0 internals. The overall size is unlikely to shrink,
though, because I'll be adding in other capabilities.
- Dennis
Philippe Laporte wrote:
Hej,
So the size of the JiBX runtime without external components,
including parser, is around 70 KB.
I realize that it has super-speed.
In the traditional speed-vs-size tradeoffs, have a lot of pro-speed
decisions been made?
Can one dream of reducing the size to 30 KB?
What's the big picture here?
Regards,
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
jibx-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jibx-devs
