[Exist-development] DOMaTeXist & refactoring

[Dmitriy S. <sha...@gm...>]

Hi every one,

The 1.4 is out! 1.6 on a way! (Le Roi est mort, vive le Roi!) ;) 

next I want to implement my old dream: one DOM-like (DOMaTeXist)
 top API for memory & stored.

I do understand that is very difficult to optimize alligator & hen, but
some sort of it should be possible. Any way, low API can be use to have
special magic.

At same time it will allow to have 
 - shared memory structure;
 - same API for any further implementation (on fly configuration as
example)
 - ... something that I can't remember, but very important staff ;)

The refactoring plan:
 - apply rule: clear name for interface, Impl suffix for class
 - move memtree to org.exist.dom & rename to memory
 - create org.exist.dom.internal & move related classes (stored nodes)
there
 - by SMALL steps create DOMaTeXist interface + deprecate (add) methods
that have same semantic, but different names at memory & stored

********************************************************** configuration

 - apply "configuration by annotations" 
( http://exist.svn.sourceforge.net/viewvc/exist/branches/shabanovd/config/src/org/exist/util/config/ )


*********************************************************** interpreter

 - add org.exist.interpreter & create interfaces (Context,
Interpreter ...) that should be a link between xquery & xsl engine
 - redesign xquery engine to split compiled tree & evaluation, after
demonstrating that technics on xslt

That's all for now, rest shouldn't touch core part. Well, not all, in
December I'll discuss phantom node integration. That will change a
little storage engine. (storage partitioning will require similar
changes any way)

That's my next 6 months plan ;) (svn, xslt, phNodes & more are not in
count)

If somebody have something more to change, please, share.

-- 
Cheers,

Dmitriy Shabanov

PS I did check my daily logs, still no plans to destroy eXist :-)