Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I was going to use Zend_Cache, but it says here that it’s not the best solution when you have a variable that is constantly being changed or updated.
What do you recommend? I want a priority queue that all users can change, update and share concurrently, without concurrency problems. This variable would live forever on the server.
Thanks!
Well I think this also depends on what backend you are using for Zend_Cache. The default file storage is probably not be the fastest solution, but Memcached might look a lot different.
But it’s important to remember that a cache is just that – it is supposed to make existing data available faster. If your shared variable should live on and you need transactions to avoid concurrency issues you will need some kind of persistence mechanism be it in a file or a database.