🚀 go-pugleaf

Hi, Maxim!

Based on the documentation, it seems to me you have three pieces to the
problem - 1) Registering all of the interested RDM / LDMs (local data
modules) and 2) Detecting updates and notifying from the list and 3)
Dealing with dead registered RDM / LDMs.

Registering an RDM probably means registering its AppServer variant,
which can be dereferenced to allow the registrar to call through the app
server disp cast of the variant's IDispatch. The registered RDM should
make available a method to pass data on what is to be refreshed.

Registering an LDM probably means registering the parameters of a socket
or other communication interface to which the LDM will respond by
refreshing its contents as directed.

(2) is fairly simple except in the presence of (3), so every send should
be wrapped with as much exception handling logic as possible. There may
be other ways to detect RDM / LDM which fail to unregister on
termination, but I don't know off hand what they are.

I hope this provides some ideas.

------
Mark Cashman (TeamB - C++ Builder), creator of The Temporal Doorway at
http://www.temporaldoorway.com
- Original digital art, writing, music and more -
C++ Builder / JBuilder Tips and The C++ Builder Programmer's Webring
(Join us!)
http://www.temporaldoorway.com/programming/index.htm
------