Please report new issues athttps://github.com/DOCGroup
The CosEC uses the real-time event service as its back-end, it can exploit this service to implement filtering between multiple CosEC. The current example is hard to read and the output is not clear, it should be improved to clearly highlight this feature.
IMHO both the CosEvent examples should be revamped this way - 1. write a PushConsumer_ServantBase and PushSupplier_ServantBase. .This way it will be easier for application developers to write suppliers/consumers because that will handle all the common code like getting the proxypushconsumer, and disconnecting when done etc. 2.I only managed to put the base class for the CosEC in the CosEvent_Utilities and thats used by the EventService and the factory. i have to change the CosEC_Basic example to use that as well. 3.CosEC_Multiple: If we use the servant base classes for this example then it will thin down the code a lot. the same will happen for CosEC_Basic too. 4.Additionally i have to debug the run_test.pl files for this example.
to pool