Greetings, I've been investigating a way to properly unlock TNT_APPLICATION_SHARED_VAR/TNT_APPLICATION_GLOBAL_VAR (global application) variables, because when one is used every call to a component that shares it gets blocked until the component call that locked it first ends.
I found applicationunlocker.h, but the class ApplicationUnlocker "Unlocks the application (and session) as long as the object is in scope." (comment in the same file about the class) which is an overkill for me and breaks my global session variables in use, session variables can block all the way since they only affect the one browser-connection using it and inherently prevent it from doing lots of operations on the server at the same time. Then again if I sort my code to use the global application variables before using the session variables I can manage. Can it be done so the ApplicationUnlocker class unlocks application variables alone? or are they are dependent? Regards. Joan ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
