ksbhaskar
commented
5 years ago Although YottaDB is not thread-safe, the forthcoming YottaDB r1.24 will include an API to allow a multi-threaded application to call the single-threaded YottaDB engine, and we are using that API to create a wrapper to allow Go applications (Goroutines are inherently multi-threaded) to use YottaDB. Note that YottaDB development now occurs on Git:Lab (https://gitlab.com/YottaDB), with the work mirrored to GitHub.
For more information, see https://yottadb.com/yottadb-support-for-multi-threaded-applications/
Regards – Bhaskar
On 1/2/19 5:01 PM, Kaoe wrote:
Currently I use GTM through a socket server in java that implements a network layer compatible with the Intersystem Cache. Although GTM supports calls directly on its APIs using JNI / JNA I could not implement this way because it is not treadsafe. So I open mumps command system processes for each connection, which becomes cumbersome, and although it works fine for more than 3 years I would like to improve this implementation. I would like to know if YottaDB is treadsafe in API calls, as I was interested in porting my GTM application to YottaDB.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/YottaDB/YDB/issues/350, or mute the thread https://github.com/notifications/unsubscribe-auth/AAiqeh40ALCyW2gzyQih8SPbj8W6vIwAks5u_SxUgaJpZM4ZnS0C.
-- YottaDB - Rock solid. Lightning fast. Secure. Pick any three.
Currently I use GTM through a socket server in java that implements a network layer compatible with the Intersystem Cache. Although GTM supports calls directly on its APIs using JNI / JNA I could not implement this way because it is not treadsafe. So I open mumps command system processes for each connection, and although it works fine for more than 3 years I would like to improve this implementation. I would like to know if YottaDB is treadsafe in API calls, as I was interested in porting my GTM application to YottaDB.