Looks like our design for dealing with multiple values is going to entail a
big performance hit because a roundtrip to the server is needed in order to
get each value.
I suggest that we add a way to request all the elements in a seqeence. So in
addition or instead of xxx_iterator, there is xxx_sequence, which returns a
sequence of all the elements. THis allows the server to send all the elements
with one roundtrip. I looked at some performance numbers from Orbix, and
looks like this would be a big win.
Can you run a similar experiment with Orbeline. Compare the time to request
10 elements using the iterators (basically 12 rountrips to the server, one to
get the iterator, 10 to get the elements, and one to destroy the iterators),
and to receive the 10 elements in a sequence.
Depending on the performance timings we should consider eliminating iterators
(Argh!), and using sequences to perform queries on multi-valued attributes.
We would still keep the add_xxx and remove_xxx method. The sequences would be
used only for query.
If we go back to using sequences, we need to implement our own sequences. Is
that correct?
Pedro Szekely
USC/ISI, 4676 Admiralty Way, Marina del Rey, CA 90292
Phone: 310/822-1511, Fax: 310/823-6714
URL: http://www.isi.edu/isd/szekely.html