hi:
Reading about many data access layer design on the forum, making me rethink about my approch. I read that many people use caching technique to bring the database file into memory, then access it from there.
I followed different approch, which is very similar to accessing RDB using
JDBC. I have little experience using IO and flat files. I don't know if it is the right approch or not, and your feedback is greatly appreciate.
here is how I do it:
First I don't bring anything to the memory, performance is not an issue for me at this point. Scalability and extensibility is more important.
In my data access class, every method that needs to access or modify the database, inside the method body, I open a stream to the database file, do all the business logic the method has to do, then close the stream.
It is the same way I do it accessing RDB.
I am not implementing any network support, or locking mechanism at this time. I am taking it one step at a time. So, if anyone think that my approch will be inappropriate implementing network support, or locking please warn me.
thank you
[ May 11, 2004: Message edited by: Hanna Habashy ]