Re: Why does Barracuda choose the way to parse the whole page (*ML) to a doc?

Jacob Kjome <[email protected]>
Newsgroups gmane.comp.java.enhydra.barracuda.general
Message-ID <[email protected]>
I really suggest that you post these questions to the xmlc list at 
xmlc.enhydra.org.  Barracuda, theoretically, deals with any DOM structure 
that implements the w3c dom.  In practice, pretty much everyone uses XMLC 
and it is used by Barracuda's examples by default.  So, Barracuda has 
little to say about the implementation of the dom structures except that it 
expects them to be w3c dom compliant.

I still don't fully understand the "squeezing" that you speak of, so you 
are going to have to be a bit more clear on that.  Again, the xmlc list 
would be a better place to ask.  There are people there that would be much 
better qualified to answer your questions.  Please don't take this as a 
lack of interest.  I just can't speak to it very much.  It is possible 
that, come Monday, some of the other people on the Barracuda list will have 
more to say about this, so be patient.  The list is usually pretty silent 
over the weekend.

Jake

At 01:04 PM 3/15/2003 -0500, you wrote:
>Thanks for your reply. Please look my messages as
>follows:
>
>  --- Jacob Kjome <[email protected]> wrote: >
> > Are you thinking of the LazyDOM feature of XMLC?
>
>Not exactly. I am more interested in Barracuda's
>framework. I like its architecture more than Struts. I
>want to make sure the performance comparison between
>these two. If Barracuda parses the whole doc tree,
>then they will perferm similarly.
>
> > That will make it so that
> > nodes don't get opened until they require
> > processing.  Unfortunately,
> > Barracuda really doesn't make use of the
> > LazyDOM....at least not through
> > BTemplate.
> >
>
>What doc structure does Barracuda use?
>
> > Maybe you can explain a little more what you have in
> > mind.
>
>I like to parse the dynamic components such as BTable
>to some light weight data structure(not Node in
>w3c.dom) and squeeze all other nodes(static part) to a
>few idled data nodes(just some strings). Normally,
>most of the nodes will be squeezed into a few strings.
>So the doc tree will be much smaller.
>
>In LazyDOM, there is no such squeeze. I don't know if
>other "DOM" does this.
>
>However, the new data tree cannot be a w3c.dom
>Document.
>
>
> >You might also
> > want to post your question to the XMLC list since it
> > may be more relevant
> > there.
> >
>
>I will discuss this to there after I understand more
>about the parser used in Barracuda.
>
> > Jake
> >
> > At 12:14 PM 3/15/2003 -0500, you wrote:
> > >I am trying to understand Barracuda/XMLC right now.
> > I
> > >am wondering why XMLC parse the whole *ML to a
> > >Document. The doc tree is so big. Why don't just
> > parse
> > >to a smaller doc tree? So the perfomance will be
> > >improved significantly.
> > >
> >
> >______________________________________________________________________
> > >Post your free ad now! http://personals.yahoo.ca
> > >_______________________________________________
> > >Barracuda mailing list
> > >[email protected]
> > >http://barracudamvc.org/lists/listinfo/barracuda
> >
>
>______________________________________________________________________
>Post your free ad now! http://personals.yahoo.ca
>_______________________________________________
>Barracuda mailing list
>[email protected]
>http://barracudamvc.org/lists/listinfo/barracuda
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.