Sorry, one more thought. It would be good to see an example of client code that would use this facility. Especially since the facility become a part of the parser API. Also, it would be a good starting ground for a sample.
Ted On Wed, 2002-01-09 at 09:04, [EMAIL PROTECTED] wrote: > Hi Ted, > > >I assume that there is a default GrammarPool implementation per parser > configuration. How does an application store a grammar pool so that it > can avoid re-creating one? > > My suggestion would be to have it query the appropriate property on the > Configuration on the first run, then set the property explicitly on > subsequent runs. Do you think that would work? > > >How can an application create a grammar pool > that is locked to a particular set of grammars? > > If it defines its own it can completely control what grammars get in to the > pool. > > But a related question is how we go about permitting grammar preparsing in > XNI--grammar caching doesn't make too much sense until you can preparse > your grammars before going live. I guess making some sort of GrammarParser > class in the org.apache.xerces.parsers package might do the trick. Any > other suggestions? > > Finally, I suspect we'll want to look at making sure our grammars and > default grammarPool are serializable. > > >Is a grammar pool sharable amongs multiple parser instances? > > I think the default one should be, but the general case would be up to the > appplication. > > Cheers, > Neil > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
