Re: [Vtd-xml-users] Random Access Proposal (take 2)

[Mark S. <ma...@Sc...>]

Rodrigo Cunha wrote:
> I understand NodeRecorder was not intended to be kept in large numbers, 
> but I think that should exactly be the idea of a random access API: a 
> lightweight way of keeping a bunch of bookmarks in the datastructure the 
> programmer wants, not in the structure we want, or something...
> 
> Your API is nice for somewhat serial processing, not for true random 
> access, using pre-build hash tables, for example, or trees, or whatever. 
> I could built a wrapper around NodeRecorder implementing a simplier API, 
> but that would be really clumsy.
> 
> My API, while incomplete, is much more simple, and flexible also... it's 
> also rather light. I would like to learn about other opinions on the 
> subject, since we are probably both too used to our way of doing things 
> to be impartial.

It would be most helpful to me if I could index arbitrary element 
indexes and start and XPath query from one of these indexes. I would 
cache these indexes in a Map with key: some unique ID, value: some sort 
of vtd-xml node index.

For most of the applications I use XML for, this would be the only way 
to get acceptable performance. Ultimately, without this I would not be 
able to consider using vtd-xml for these apps and I would be forced to 
use an xml - Object mapping tool.

I've been using and helping maintain/fix a number of XML - Object 
mapping tools over the years. It's been an interesting area of study for 
me. Please free me from the insufferable weight of those chains :-)

Cheers.

-- 
http://www.ScheduleWorld.com/
Free Google Calendar synchronization with Outlook, Evolution,
cell phones, BlackBerry, PalmOS, Exchange, Mozilla, Thunderbird,
Pocket PC/Windows Mobile. Also sync tasks, notes and contacts!
WebDAV, vfreebusy, RSS, LDAP, iCalendar, iTIP, iMIP support.