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

[Jimmy Z. <cra...@co...>]

Rodrigo,
    Can you explain the hash table a bit more? I am especially interested
in when it would helpful to you... also I would like to know if you think
there are alterantives...

    From my perspective, offering something you described
is definitely what we strive to achieve, however, when we design/enhance
an API, everything we add can potentially be a double-edged sword,

    Take nodeRecorder as an example..it offers some degree of random
access, but if not used properly it will consume much memory, also I have
been a bit busy lately with some other stuff..

   let me get to some of your old emails the next few days and get back to 
you...

----- Original Message ----- 
From: "Mark Swanson" <ma...@Sc...>
To: <vtd...@li...>
Sent: Wednesday, February 28, 2007 8:11 AM
Subject: Re: [Vtd-xml-users] Random Access Proposal (take 2)


> 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.
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share 
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Vtd-xml-users mailing list
> Vtd...@li...
> https://lists.sourceforge.net/lists/listinfo/vtd-xml-users
>