Christian P�cher

I took a BitSet to indicate a used record. It has this nice nextClearBit(int arg) method, which saves me a loop and I expect it to work in O(1) in contrast to O(n) of the linear search you suggested.

chris

Originally posted by Alex Sharkoff:
I agree with Thomas. I guess your specification also states that : You may assume that at any moment, at most one program is accessing the database file; therefore your locking system only needs to be concerned with multiple concurrent clients of your server.

Yes, of course you are right. Somehow I did not really understand that sentence in the first place.

Thanks a bunch, Chris

Hi there,

I have one requirement I would like to crosscheck with your help.
"... because the data must continue to be manipulated for reports using another custom-written application, the new system must reimplement the database code from scratch without altering the data file format."

I understand this requirement, that I have to be able to handle concurrent read/write access to the database file from outside of my application, which could be a bit tricky to implement. Do you agree or do you think, there will be external read-only access?

TIA, Chris

I guess .gif files go into code/ because they belong to "source code and related parts". Just make sure you can load your .gifs from an executable .jar as well as from the filesystem.

Well, I understood the code within 30 secs and when you write documentation for the method, I would have been even faster. My assignment - as well as my experience - says you should prefer clarity over minor speed improvments. The code is readable, so it is ok. If you are really concerned about speed, I would take a profiler and fix hotspots first.

HTH, chris

I guess with those gifs and html you are referring to your javadoc documentation. Well, my assignment says I should put it into a directory called docs/javadoc/. Take a look into your assignment, it is the safest source of wisdom for you. :-)

Good Luck, Chris

Javadoc lists only public and protected classes and methods by default. You may change that behaviour by setting -public -protected -package -private when calling javadoc. In your case -package might be appropiate.

HTH, chris

This specification calls for a preferences dialog, can't you hear it shouting?
Have a default URI for your DB on deploy and make it configurable in the preference dialog. If you want to, you could save the URI in a Properties file.

HTH, Chris