Hi Rickard!
Rickard �berg skrev:
> However, when a class is neeed, as is the case during serialization, it
> will be asked since it is the first in the row, and consequently there
> will be a lot of hashtable misses. And that is expensive. So, we might
> want to eliminate the beanloader altogether. That *could* be it. Will
> have to test more.
Probably have you already thought of this but...
Would it be possible to only have one hashtable with all classes in an ordered
sequence with classes from beanloader first and then classes from apploader and
serverloader. (I guess systemloader is handled in a more standard way if no hit
from other loaders?). In this way you would only have one hashtable to search.
Problem is where to have this hashtable and how to make the different loaders to
fill it up, or?
/Lennart
--
________________________________
Lennart Petersson
Benefit AB
Tyn�sgatan 14
S-652 24 Karlstad
Phone: +46 (0)54 177253
mailto:[EMAIL PROTECTED]
Yahoo! Messenger, my nickname is: en_grillad_special
http://www.benefit.se
