Sorry I wasn't clear, the parser isn't itself multithreaded, the Java
process that needs the services of a plucker parser is. I mentioned that
the consuming app is multithreaded because this influences the viability
of any *plucking* solutions it would use, and not because the parser itself
is multithreaded. There are no shared resources between parsers instances
within each thread, it is stingy on resources use, and is patterned to
allow easy distribution of the *plucker* work (one can parse on the server
or parse on the client, for example). It doesn't create and manage threads
itself. The code isn't available now and I'll look into releasing it (if
anyone is interested, of course).
"Dave
O'Neill" To: Plucker Development List
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
cc:
07/12/2001 Subject: Re: Java Parser
09:51 AM
Please
respond to
Plucker
Development
List
On Thu, 12 Jul 2001, Dale Applegate wrote:
> I have written one. Here is why: I wanted to dynamically pluck,parse,
> and package a plucker db from a multithreaded Java process (A Java web
> application), and send this db over the internet to a waiting Hotsync
> conduit or directly to the browser. Writing a parser in Java seemed
> the smoothest way to accomplish this, so I wrote one (It is a little
> off from being complete, but it has a core functionality). I
> originally asked the question because I was simply curious if anyone
> else has done it, not because it *should* be done.
Is your code available anywhere under a license that would allow others to
make use of it? I'm interested in seeing your multithreaded
implementation.
-dave0
--
aitchteeteepeecolonslashslashtripledoubleyoudotevilplotdotorgslashtildedave
"Not much call for a barbarian hairdresser, I expect. I mean, no-one
wants a shampoo-and-beheading" -- ``Sourcery'', Terry Pratchett
