marius popa wrote:

>On Fri, 08 Oct 2004 09:09:50 -0000, Roman Rokytskyy <rrokytskyy@...> wrote:
>
>
>>
>>
>>>To fix this would mean much more troubles
>>>compared to keeping a thread-per-connection-at-a-time principle.
>>>
>>>
>>Just to make it clear: you can access a connection from multiple
>>threads, but not simultaneously. When one thread works, other should
>>wait.
>>
>>
>>
>
>I think this should be added to the faq :)
>
>
>

The Vulcan engine supports multiple threads per attachment, though the
remote interface is restricted by the wire protocol to a single active
thread per attachment (parallel threads automatically block until
serviced). We are considering allowing multiple threads per
transaction, but I think we won't on the basis that this usage would be
rarely used, and on aggregate isn't worth the cost of the necessary locks.