You should not have to worry. The two possible culprits are the VOCache which 
should be thread safe done by a semaphore. The other one is the connection to 
the database. Here the connection pool removes that problem.

Hope that answers your question. I use it just as it is in a concurrent 
environment.

Norbert


> Am 01.06.2021 um 11:34 schrieb Jesus Mari Aguirre <jmariagui...@gmail.com>:
> 
> Hello all, I'm developing a tepot+voyage(mongodb) web app and I have one 
> doubt, is voyage thread safe? or do I have to take care about using a Mutex 
> because multiple teapot instances can call it.
> Thank you all! 

Reply via email to