+1, thx Johannes. BaseX has quite a powerful internal API, but JavaDoc is the only available documentation. I'll give some more feedback end of the week. Am 16.10.2012 01:57 schrieb "Johannes.Lichtenberger" < johannes.lichtenber...@uni-konstanz.de>:
> On 10/15/2012 07:12 PM, Rainer Klute wrote: > >> Thanks, Michael, for your 2 ¢! >> >> I think I have an idea now what BaseX can do and where the limitations >> are. Well, since I won't get this >> lazy-loading-while-navigating-**a-DOM-thingy anywhere, I'll have to >> reconsider my system architecture and find another solution. >> >> (A lazy loading might be an idea for a future BaseX version. :-)) >> > > Strange enough -- maybe I didn't get the problem, but I'm rather sure > BaseX can cope with this use case!? Just from a high level view it should > come down to loading pages (with the nodes) in a buffer and using some > buffer replacement strategy, plus exposing the XPath-axis and so on or at > least some navigational-methods. > > BTW: You maybe also could try using Sirix[1] and have a look into [2] for > some veeery basic documentation. I'm currently working on index-structures > and a Brackit(.org)-binding (to provide XQuery and XQuery Update Facility > mechanisms as well as temporal XPath extensions). Maybe (or hopefully) you > could get some performance boosts with SSDs in comparison to other DOM-like > storage systems. However the real benefit is that you are able to version > and persist the data together with (hopefully) in the future full ACID-safe > transactions. Would be nice if you at least could have a look into it. I'd > happily give you a helping hand if you need some precise instructions or if > you encounter bugs (however, keep in mind that I'm currently the only > developer -- and sadly I have so many ideas for features and improvements > but at the time being I'm not aware of any users). However it's open source > and I hope at some time another interested and motivated developer -- or > two ;-) joins the "team". But well, first of all I need some users ;-) At > this time I'm especially interested in API related matters. At least I've > put some effort some weeks ago in a hopefully "nice" API and am just > thinking about renaming some methods, but other than that "finalize" the > API as it is (except for future additions for sure). But for this I'd first > like to get some input, would be really great :-) However, I'd say if BaseX > provides an API cope with it, as it's industrial strength software and has > a lot of users. > > kind regards, > Johannes > > [1] > https://github.com/**JohannesLichtenberger/sirix<https://github.com/JohannesLichtenberger/sirix> > [2] > https://github.com/**JohannesLichtenberger/sirix/**wiki/Simple-usage<https://github.com/JohannesLichtenberger/sirix/wiki/Simple-usage> > . > > ______________________________**_________________ > BaseX-Talk mailing list > basex-t...@mailman.uni-**konstanz.de <BaseX-Talk@mailman.uni-konstanz.de> > https://mailman.uni-konstanz.**de/mailman/listinfo/basex-talk<https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk> >
_______________________________________________ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
