#13 Potential problem on the sequence info of the client
[Problem]
The amount of sequence information in a client (the
table of the last sequence numbers of events the client
has seen and it is sent to the server when calling
waitForEvent etc.) increases every time the client
encounter another client and never decreases during its
lifetime.
This potentially results performance loss on memory
and network traffic for long-running application.
It may be serious when any applications participating in
the dialog are using "automatically generated client ID"
because the entry will increase one by each launch
(including restart) of an application process.
[Suggested Fix]
Nothing so far.
A client need to know if any pair of Source ID and
Session ID is no longer used to invalidate the
corresponding entry, but there's no apparent way to do
so.
[Workaround]
Periodical restart of the client application may work.
Using some long-lasting identifier as the Source ID of
each participating application instead of generating new
one each time may alleviate the increase of useless
entries.