• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Justifications in the design document

 
Andras Nemeth
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
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!
Ban
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
Posts: 275
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
Had a little look around and the following should help:
http://www.javaranch.com/ubb/Forum1/HTML/000831.html
Good luck
Ian

[This message has been edited by Ian B Anderson (edited November 01, 2001).]
 
Peter den Haan
author
Ranch Hand
Posts: 3252
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic