thread summary: On Cerebro, Telepathy, yokes and whites
ypod at mit.edu
Wed Jun 11 14:22:10 EDT 2008
This is a summary (a la Michael) of the cerebro/telepathy thread.
Pol brought up the issue of how the collaboration stack is currently
implemented, that there should be a dead-simple networking API for
activity development and proposed someone taking the lead in
implementing a connection manager for cerebro (which currently offers a
Ben suggested that there is no need to abstract telepathy further
because it's an abstraction layer in itself. Instead, API changes should
be proposed, if any exist.
Ricardo suggested that there should be someone working on a cerebro
connection manager in parallel with jabber.
Marco and Tomeu agreed that there should be a cerebro connection
manager, Marco conceded to getting cerebro in joyride, but disagreed
with adding an abstraction layer between telepathy and sugar/activities
on the basis that telepathy is abstraction layer in itself and we must
live with what is currently available for lack of resources and because
compromises are often made in large software projects.
Scott brought up the issue of children invariably trying to develop a
multi-player game on sugar and failing because of the complexity of the
collaboration API. Marco agreed with this problem and recognized the
need for a python layer above telepathy/cerebro that can be invoked
without DBus, while a lower level DBus-based API will be used by
non-python activities. Both Marco and Scott saw the need for extensive
tutorials and examples on how to use any networking API for activity
Kim would like to figure out how to make progress on cerebro.
Robert characterized telepathy primarily as an API to a variety of
functionality and different communication mechanisms, recognized some
problems in the implementation and the need for cerebro as one of the
plans to deal with those problems. He also went through the history of
how D-Tubes and stream tubes came about and noted that the requirements
were not really clear when their (D-Tubes and stream tubes)
implementation started. He also recognized the need to hide some of the
complexities of network programming by adding a simplifying layer on top
of telepathy, or by extending the current telepathy API.
Finally, Morgan went through the history of how the Presence Service was
implemented, that it predates the use of telepathy and that it contains
some "interesting", to put it politely, design aspects. He also went
through his efforts to simplify the implementation of collaboration in
activities by pushing the telepathy functionality from the activities
into the PS where possible and his plans to simplify further
collaboration in activities.
Tomeu also suggested getting this summary together (thanks!) and that it
may make sense to separate discussion on the API from discussion on the
I hope I captured the most important parts of this threads, feel free to
blame me if I failed in any parts.
MIT Media Lab
Tel: +1 (617) 459-6058
More information about the Devel