[Sugar-devel] Collaboration support for sugar web activities

[Lionel Laské]

Just to let you know status of our work on Sugarizer (instant)
collaboration.
We've decided to rethink from scratch what collaboration means. So we've
wrote a functional overview of the expected features [1]. Suraj has started
to implement a prototype with WebSockets using node.js. It's here [2].
My idea is to integrate this in Sugarizer, then later to try to interface
it with current Sugar collaboration.
In fact it's a bottom-top approach vs a top-bottom approach, sure that both
approach could meet in the middle :-)

              Lionel.


[1]
https://docs.google.com/document/d/1FZRv0gSV--5Y4dvV9C9dk9K-LT7kEQEwQmX_xVX9H-s/
[2] https://github.com/surajgillespie/SugarPresenceAPI


2014-02-20 19:24 GMT+01:00 Emil Dudev <emildudev at gmail.com>:

> On Wed, Feb 19, 2014 at 1:17 PM, Daniel Narvaez <dwnarvaez at gmail.com>wrote:
>
>> With making the protocol more complex do you mean that the activity would
>> send both presence information (the registration stuff you mention) and
>> messages for other clients on the same channel? Or would registration still
>> go through the shell?
>
> Mostly yes.
> An activity knows it's color, it's bundle, it's name. I'm not sure if it
> knows it's activity_id, but it wouldn't be hard to get it.
> I'm trying not to think of it as 'buddy creates such activity', but
> 'activity is created/shared' and 'buddy joins activity'.
> I think this would be a good way to implement it.
>
>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20140221/21fd8789/attachment.html>