Using a database for this purpose is the most general solution. We do not have another mechanism for that and the reason is that everybody would want a different locking mechanism. For example is a client is using a variable should all other clients be locked and prevented from accessing the variable? What about is two variables are somehow related? Should the second variable be locked when the first one is used? How do we specify which ones are related?
If you store variables as db records all these problems are solved by the transaction mechanism. Massimo On Mar 15, 3:08 am, Jason Brower <[email protected]> wrote: > I want to have a variable(name) that can be read and manipulated by all > active sessions. > This is useful for a timer that I want to implement. It would make it > easy for me to still have access by multiple users if needed. > Do I really need to save it to a database first? (It would be much more > laborious that I expected.) > Best Regards, > Jason -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
