Yes, your response broadly addresses my question. But to be specific:

If the modules are all part of the same page, they can share a pointer to the LightstreamerClient object and each one can use the same object to add its subscription requests, together with its listeners.
But there is no lookup method by which a module can see if there is already a LightstreamerClient object in the page. This should be implemented at application level.
So the parent module has done the following:

  1. It subscribes to ONE topic 'parentTopic'. here's pseudocode:
    1. const client = Lightstreamer.LightstreamerClient(lsServer, adapterSet)
    2. ....client.xxx0 = yyy, etc
    3. ....client.xxx1 = yyy, etc
    4. const item = 'json::: + 'parentTopic' + '::::${some string} + user + '\')
    5. const subscription = new Lighstreamer.Subscription('RAW', [item], '['Body']);
    6. .client.subscribe(subscription)


The child module needs to create/subscribe to ANOTHER topic say ('childTopic') which receives another set of data with a different structure.

I assume, the child module just needs the handle of the client the parent has created (see 'client' above) and nothing else. If so (or not so) What are the EXACT sequence of steps for the child module to subscribe to its 'childTopic'?

Thanks!