During the text scan, resources may be locked, depending on what you do
exactly. Any threads that hit the same resources are likely to block
until your function returns.

One of Vulcan's innovations is a superior mechanism for making it
thread-safe, and making it far less likely that one thread can block
others accidentally.

On the other hand ...

I re-read you original post. I still believe that your problem would
likely benefit from application of the Vulcan re-write. But I believe
that I may have overstated by saying you "need" it.

On Fri, 2005-03-11 at 08:54, Daniel Albuschat wrote:
>
>
> On 11 Mar 2005 07:29:46 -0600, David Johnson <d_johnson@...> wrote:
> >
> > To do this, you will need to start with the Vulcan core. It is much
> > more thread friendly than current releases. Unfortunately, it is also
> > incomplete and in a state of constant flux.
>
> I *need* to start with the vulcan core?
> Well, all threaded stuff is hidden from FB and the only blocking function
> will be the one actually getting the search results, so it looks like it'd be
> mostly free of threading complications to FB, won't it?
>
> > Good luck!
>
> Thanks :)
>
> Bye,
> Daniel
>
> --
> eat(this); // delicious suicide
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>