Meetings2011-06-30¶

Conditional Sending of Events¶

Only send events if someone is receiving

Requirements¶

• Save Bandwidth?
• Save data/event production cost?

Discussion and some Implementation Ideas¶

• Implementation should probably not depend on a nameservice
• This is strictly an optimization; may not be available for all transports
• Events/callbacks would be generated by participant's connector
• Callbacks in listener/informer for channelEmpty/channelPopulated
• Special kind of "meta-event" for channelEmpty/channelPopulated
  • Implementation detail: enabling and disabling of these events could be handled within connector's notification of client-installed filters

Inter-Segment Communication¶

Documentation¶

• Example program (C++)
• Wiki page

Note: implementations of configuration mechanism in Java and Python have to be improved to support this

Use-case Analysis Presentations¶

Additional Topics¶

• Feature #174
• Bug #390