Ivelin Ivanov wrote: <snip/> > > The main problem with Daniel's contribution is that the whole document > > has to be buffered in a DOM before any decision can be taken : it's like > > going back to the slow times of Cocoon 1. But we could imagine some > > smarter implementations based on partial buffering using compiled XML > > and things like STX (http://www.gingerall.cz/stx/index.html) to avoid > > complete buffering. > > Daniel acknowledged this weakness and he's willing to fix this, provided > there is enough interest in the > xpath selector and he gets some direction. I can't remember that I have volunteered to do that, I mentioned caching, but partial buffering is another matter.
Actually, my current position is that for the uses cases I have discussed, I believe that the efficiency gain in using partial buffering is rather small while it seem quite complicated to implement (at least, I couldn't find any simple designs). So for the moment I think I use my time better if I'm concentrating on form handling in Cocoon. But if anyone provide me with use cases where partial buffering would lead to a major performance gain or design ideas that would make it a more realistic effort to implement and integrate in Cocoon, I will happily change my mind. And I would of course try to contribute in design discussions, if anyone would like to implement pipe-aware selection with partial buffering. <snip/> /Daniel Fagerstrom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
