<div dir="ltr">Interesting! Are you planning to use a js actitvity or a python one as client?<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 18 January 2014 01:21, Emil Dudev <span dir="ltr"><<a href="mailto:emildudev@gmail.com" target="_blank">emildudev@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Busy month...<br><br></div>Anyway, I checked out telepathy and tried to fix the many protocol problems. Sadly, I gave up pretty easily. I suppose it would be easier to rewrite the whole process from scratch.<br>
<br></div>Today I was able to recreate the basic functionality of TogetherJS' server. From a nodejs server, I rewrote it in python (using gwebsockets). This will give me the ability to customize it freely.<br><br></div>
Tomorrow I plan on building the basic invitation process using web sockets. I suppose it will be more reliable than telepathy. And it would possibly be better for an Android app or other systems with limited functionality.<br>
<br></div>About WebRTC: I really think that peer-to-peer connections are needed. But at this point, I'll go with client-server connections.<br><div><br>gwebsockets: <a href="https://github.com/edudev/gwebsockets/tree/master" target="_blank">https://github.com/edudev/gwebsockets/tree/master</a><br>
websocket-server: <a href="https://github.com/edudev/web-reply" target="_blank">https://github.com/edudev/web-reply</a><span class="HOEnZb"><font color="#888888"><br><br></font></span></div><span class="HOEnZb"><font color="#888888"><div>
Emil Dudev<br></div></font></span><div><div class="h5"><div><div><div><div><div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">
On Sun, Jan 12, 2014 at 8:51 PM, Daniel Narvaez <span dir="ltr"><<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div>On 12 January 2014 19:01, Emil Dudev <span dir="ltr"><<a href="mailto:emildudev@gmail.com" target="_blank">emildudev@gmail.com</a>></span> wrote:<br></div><div class="gmail_extra"><div class="gmail_quote">
<div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr"><div><div><div>About the telepathy part to send only the invites and establish the connection:<br></div>I can't seem to be able to complete the invitation accepted process. Sometimes it works, sometimes not (mostly not). For normal sugar activities it's the same (with the exception that with them it mostly works, at least I think it works).<br>
</div><div>Exchanging the TogetherJS ID is not a problem. The invited user can't seem to connect to the telepathy channel properly.<br></div>As you noted above, it's a protocol mess.<br></div><div>If telepathy is completely dropped for web activities, then a question arises: how to send the invite with the unique ID?<br>
</div></div></blockquote><div><br></div></div><div>I don't know the details of the current invitation protocol. I suppose you could register a "private" activity with the server and then send a token to the invitee. Making this up as an example, not really well thought :)<br>
</div><div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Also, I still don't like using 1 server and having everything else depend on that 1 server. The server would most likely have to process a lot of traffic.<br>
Would it be possible to use a peer to peer connection with web sockets? Browsers don't support this, with reason. But if sugar's core is used, it should be possible.<span><font color="#888888"></font></span></div>
</div></blockquote><div><br></div></div><div>Did you investigate WebRTC? If nothing else I suspect it would allow to exchange data between peers. I'm not sure if it provides any facility that we could use to share presence information, i.e. a shared buddies+activiities list. That's the really hard problem to solve if you want fully p2p communication.<br>
</div></div></div></div>
</blockquote></div><br></div></div></div></div></div></div></div></div></div></div></div></div>
</blockquote></div><br><br clear="all"><br>-- <br>Daniel Narvaez<br>
</div>