I like the s/w very much and want to incorporate it in a website but am concerned that it might not be applicable in a multi-user environment. Flat file data storage is notoriously hard to manage in a lock/update/unlock sense. Is ORS properly coded to handle mulit-user?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Oh yeah. It was designed for multi-user setups. It has a lock system that manages the multi-user aspect fairly well. I have used it with up to 50 users, but know of people using it with 100 or so users, but if you got to lots and lots of simultaneous users, it would start to bog down (but should still respect the locking system).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi … we have 200+ users on a system that has been running for 8 years (with updates). Not a lot of users are on at once, but no data corruption to report so far.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I like the s/w very much and want to incorporate it in a website but am concerned that it might not be applicable in a multi-user environment. Flat file data storage is notoriously hard to manage in a lock/update/unlock sense. Is ORS properly coded to handle mulit-user?
Oh yeah. It was designed for multi-user setups. It has a lock system that manages the multi-user aspect fairly well. I have used it with up to 50 users, but know of people using it with 100 or so users, but if you got to lots and lots of simultaneous users, it would start to bog down (but should still respect the locking system).
Hi … we have 200+ users on a system that has been running for 8 years (with updates). Not a lot of users are on at once, but no data corruption to report so far.
Thanks for the quick replies. My mind is more at ease now. I'll be running it in a Joomla iframe with a user base of between 150 - 200.