<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I'm sorry. I don't understand you. Currently collaboration in
locations with a school server is done by ejabberd. This resulted
from the fact that the original mesh and later ad hoc networks did
not support the requirements of actual deployments. This means the
software supports XMMP to connect with jabber servers.<br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 07/24/2016 12:03 PM, Sam Parkinson
wrote:<br>
</div>
<blockquote cite="mid:1469354613.3950.1@smtp.gmail.com" type="cite">I
actually don't want to use XMPP for the new collab system. I
don't care how nice the library is. Telepathy isn't the best,
maybe pyxmpp2 or nbxmpp are better. But xmpp is not the right
protocol for sugar.
<div><br>
</div>
<div>Say you want to solve problem 2 and have a shared group
channel. You could use xmpp, but then every message you send
has a huge xml wrapper around it adding metadata. The metedata
is useful for an IM application, but not very useful at all for
Sugar. So then maybe you use a stream tube over xmpp? Well (at
least for telepathy - but it is probably due to the xmpp
protocol), you need to estabilish a group chat before you can
call the stream. Boom, added 200loc and another few round trips
before the activity starts collaborating.</div>
<div><br>
</div>
<div>You also say that XMPP is standard, which is nice. I like
standards too. But the way sugar uses xmpp, there is little
point to it being standard. "Standard" in Sugar content means
you choose between ejabberd, jabberd and parsody. You can't
collaborate between Write activity and $other_word_processor.
You can't collaborate between Bibliography activity and
$other_bibliography_manager. Even if you could, that would be
based on the "Bibliography Manager Collaboration Standard" - not
XMPP.</div>
<div><br>
</div>
<div>Sugar has generic applications - not chat clients. We need
a generic application protocol - not an IM protocol.</div>
<div><br>
</div>
<div>Sebastian raised the point of backwards compatibility for his
use case. I think that we can provide a chat bridge no matter
the technology. We could also just expose chat activity inside
traditional dekstop environments, as your work continues to move
towards.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Sam</div>
<div>
<div><br>
On Sun, Jul 24, 2016 at 6:07 PM, Tony Anderson
<a class="moz-txt-link-rfc2396E" href="mailto:tony_anderson@usa.net"><tony_anderson@usa.net></a> wrote:<br>
<blockquote type="cite">
<div class="plaintext" style="white-space: pre-wrap;">XMPP is a standard protocol (originally called jabber). Currently,
collaboration is supported on the schoolserver by ejabberd. This
implementation has not been changed for years AFIK.
In any case, implementation of collaboration probably should be XMPP
compliant to maintain maximum compatibility with what we are doing now.
Tony
On 07/24/2016 08:04 AM, Sebastian Silva wrote:
> Currently I can use gajim to chat to Sugar users (it will trigger a Chat
> activity invitation).
>
> This is the level I meant when I said "backward compatible".
>
> I don't know if python-nbxmpp or python-farstream support some sort of
> tube, but for sure the api won't be the same as telepathy. Those are
> gajim's foundations.
>
>
> El 24/07/16 a las 00:59, <a moz-do-not-send="true" href="mailto:sam@sam.today">sam@sam.today</a> escribió:
>> How? Who understands how the current code works? Can we pass xmpp
>> channels from gijam's xmpp library to telepathy?
> _______________________________________________
> Sugar-devel mailing list
> <a moz-do-not-send="true" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
> <a moz-do-not-send="true" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
_______________________________________________
Sugar-devel mailing list
<a moz-do-not-send="true" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a moz-do-not-send="true" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>