File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Developer Certification (SCJD/OCMJD) and the fly likes Justifications in the design document Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Developer Certification (SCJD/OCMJD)
Bookmark "Justifications in the design document " Watch "Justifications in the design document " New topic

Justifications in the design document

Andras Nemeth
Ranch Hand

Joined: Jul 31, 2001
Posts: 80
I just started to write my design document. (Of course, first
I made the application, as usual Although, I spent many days
on the design, before.)
At lock I described that I use HashMap and explained why it
is a good choice. But, I can not say it is better than Hashtable.
(Of course I made HashMap synchronized!) Can any one give me
some idea what is the difference between HashMap and Hashtable
(except null value and synchronization)?
Thanx a lot!
PS: I opened this topic in order to ask all the problem with
the design document. More questions and answers are welcomed.
Ian B Anderson
Ranch Hand

Joined: Jun 26, 2001
Posts: 275
Had a little look around and the following should help:
Good luck

[This message has been edited by Ian B Anderson (edited November 01, 2001).]
Peter den Haan
Ranch Hand

Joined: Apr 20, 2000
Posts: 3252
Originally posted by Andras Nemeth:
(Of course I made HashMap synchronized!)
If you mean you used Collections.synchronizedMap(), I'm willing to bet a beer on the fact that either your code is not threadsafe, or the HashMap does not need to be synchronized at all.
In any case, good reference Ian. In fact I suspect Sun would love to deprecate Hashtable, Vector and Enumeration, but they are still deeply entrenched in quite a few APIs.
- Peter
I agree. Here's the link:
subject: Justifications in the design document
It's not a secret anymore!