Hi,
I see everyone mentions using Hashtable, is there any reason to prefer it to
HashSet?
At least some of the approaches for using it, and I think Craig's is one of
them, are presenting us with fairly static object, initialized during
Controller servlet initialization.
Thus, syncronization features of Hashtable are in many cases irrelevant and
represent overhead.
Even in rare case when sync is needed, it can be added specifically in the
code.
I also doubt anyone here runs JDK 1.0 on their development or production
computers.
So what is the reason then.
Thanks,
Vadim.
-----Original Message-----
From: Daniel Lopez [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 28, 2000 1:59 AM
Subject: Re: Model 2, take 2
...In my case, I store factory objects in the Hashtable, indexed by
operation names...
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
