If you are using critical sections to control all the IO you will create
more and more bottlenecks in your code as your system fights over the
files. Depending on the code that responds to the failure to lock the
semaphore you will run up a lot of process cycles and/or risk
deadlocking the code.
It might be worth looking at creating an IO object that handles the disk
requests. You could have it return reads automatically and cue writes.
Of course you then have the problem of how to handle the rendezvous and
async handling. This model does allow you to easily scale up to allow
the read requests to be queued with the writes to keep the reads up to
date will little effort if required. Another benefit of this is that
you can work out resource allocation better as the IO module can run
using a periodic module and doesn't have to scale to deal with the
aperiodic calls (if you want) so you should be able to avoid the
performance ceiling .
Regards
--
Michael Hawksworth
Visual Fox Solutions
[EMAIL PROTECTED]
www.foxpro.co.uk
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
