On Thursday, October 31, 2002 9:05 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> Oh c'mon.. *no one* knows the answer to this? eeek! 8-O > > Because no one else is using it? :-) > > Actually, as the description of this class says, it's not a "parser pool", > where you can get and store parsers. Instead, it *creates* new parsers that > all share the same symbol table and grammar pool. This is useful when your > server runs in multi-threads, and each thread has its own parser to parse > similar documents (those conform to the same grammar, hence share the same > vocabulary). > *scrounges around in the API documentation* OHHHHH! My bad... :-/ > If you really need a "parser pool", it won't be hard at all to write one in > your application. A java.util.Vector or Stack would do the trick. > Oh yea I know. I've done it before. But I appreciate the tip, regardless.. :-) -- David Orriss Jr. [EMAIL PROTECTED] http://www.davenet.net http://www.codeskanks.com Please email me if you want my ICQ/AIM/IM ID's. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
