Should implement the following suggestions of Ray
Fergerson:
I can think of some things that you might do.
(1) For information that you don't need at startup,
create a low
priority thread to transverse the ontology and collect
it. The
knowledge base interface is thread safe so as long as
you don't do any
ui operation from this thread you should be ok.
(2) attach listeners to the knowledge base (a new
feature in 2.X) to get
notified when any frame changes and update your cached
information
(3) You said that writing the cached information to a
file and reading
it back in was slow. I can only assume that this is a
problem because
the ontology is very big. A java properties file
should be very quick
to load especially if you make sure that you have a
buffered reader with
a big buffer. I would also suggest reading in the file
in a low
priority thread if you don't have to have the
information at startup.
I think that trying to store this information in the
domain model is a
bad idea.
Ray
Logged In: YES
user_id=922320
Parts 1 and 2 are done. Part 3 is lower priority, to do
after demo.