Meetings2011-06-30 » History » Version 5

S. Wrede, 06/25/2011 10:50 PM

1 1 J. Moringen
h1. Meetings2011-06-30
2 1 J. Moringen
3 1 J. Moringen
h2. Conditional Sending of Events
4 1 J. Moringen
5 1 J. Moringen
_Only send events if someone is receiving_
6 1 J. Moringen
7 1 J. Moringen
h3. Requirements
8 1 J. Moringen
9 1 J. Moringen
* Save Bandwidth?
10 1 J. Moringen
* Save data/event production cost?
11 1 J. Moringen
12 1 J. Moringen
13 1 J. Moringen
h3. Discussion and some Implementation Ideas
14 1 J. Moringen
15 1 J. Moringen
* Implementation should probably not depend on a nameservice
16 1 J. Moringen
* This is strictly an optimization; may not be available for all transports
17 1 J. Moringen
* Events/callbacks would be generated by participant's connector
18 1 J. Moringen
* Callbacks in listener/informer for channelEmpty/channelPopulated
19 1 J. Moringen
* Special kind of "meta-event" for channelEmpty/channelPopulated
20 1 J. Moringen
** Implementation detail: enabling and disabling of these events could be handled within connector's notification of client-installed filters
21 1 J. Moringen
22 1 J. Moringen
h2. Inter-Segment Communication
23 1 J. Moringen
24 1 J. Moringen
h3. Documentation
25 2 J. Moringen
26 1 J. Moringen
* Example program (C++)
27 1 J. Moringen
* Wiki page
28 1 J. Moringen
29 1 J. Moringen
_Note: implementations of configuration mechanism in Java and Python have to be improved to support this_
30 1 J. Moringen
31 1 J. Moringen
h2. Use-case Analysis Presentations
32 3 S. Wrede
33 3 S. Wrede
-----
34 3 S. Wrede
35 3 S. Wrede
h2. Additional Topics
36 3 S. Wrede
37 3 S. Wrede
* Feature #174
38 4 J. Moringen
* Bug #390
39 5 S. Wrede
* Feature #389