For use, its mainly the inderminant order or creation and destruction.
There is no good way, that is portable, to make sure that things get
created and cleaned up in the right order. This is particularly sticky in
the case of the objects that were in question in this topic, e.g. the
transcoder, message loader, ect... because of the fact that if anything
goes wrong on the way down, there could be an attempt to use these things
after they have been cleaned up.
----------------------------------------
Dean Roddey
Software Weenie
IBM Center for Java Technology - Silicon Valley
[EMAIL PROTECTED]
"Arnold, Curt" <[EMAIL PROTECTED]> on 01/25/2000 10:54:28 AM
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: RE: Xerces bug submission...
Dean Roddey wrote:
>>We cannot use any sort of global object destruction to clean them up, ...
I'm really curious to know what the issues are driving avoidance of global
objects for static resources. Is it a platform issue, the indeterminent
order, or something else?
