Angular Frondend app with multiple 'decoupled' modules
Hi, from the documentation I'm having difficulty understanding the relationships between subscriptions, topics, items, fields, etc. We have a typical scenario.
- An Angular app ('parent') with various modules all written by one group of developers.
- This parent app subscribes to ONE topic. here's psuedocode:
- const client = Lightstreamer.LightstreamerClient(lsServer, adapterSet)
- ....client.xxx = yyy, etc
- const item = 'json::: + strTopic + '::::${some string} + user + '\')
- const subscription = new Lighstreamer.Subscription('RAW', [item], '['Body']);
- ....
Now add a NEW LAZY LOADED module ('child') that is built by another group of developers which has it's own topic/subscription (which?requirement with a different data structure and subscription/topic(?)
Question: what are the minimum maximally decoupled lightstreamer steps, the child must carry out to get the resources to the get new topic info? please consider two possibilities:
- IDEAL: the child is not aware of the parent lighstreamer resources so needs access to them somehow to avoid duplication and then carry out getting new topic info OR
- OK: the parent and child share a minimal state service where the parent can share minimal info with the child while maintaining maximum decoupling and maximizing resource use (no new sockets, etc)
Thanks!