<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Alright thank you all for your replies.</p>
<p>Sadly the subject is very clear on the server part which means
we'll have to cope with a server/client architecture. It's a shame
we can't use qTox, but we can always use another open-source
library that would be built on a client/server model this time.</p>
<p><br>
</p>
<p>Thanks again and keep up the good work!<br>
</p>
<br>
<div class="moz-cite-prefix">On 09/03/17 21:09, Oranges User wrote:<br>
</div>
<blockquote
cite="mid:CANjoko7jcuKSfLjq0tkbubNKZjZZzuvskMBO9aJWT_pduz0NxQ@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">Tox is a pure peer to peer networking library, so
readapting it to a client server model would require significant
rewriting of toxcore's network components and then applying that
to qtox, you'd probably be better off looking for an existing
client server networking library instead, or writing your own
from first principles.<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Mar 10, 2017 at 8:27 AM,
Thibault Lemaire <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:thibault.lemaire@supinfo.com" target="_blank">thibault.lemaire@supinfo.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hello,<br>
<br>
We're a team of 6 students working on a school project and
we would like to know some specifics about the inner
workings of tox/qTox.<br>
<br>
<br>
<b>About the project :</b><br>
<br>
It is an open subject which goal is to put us in a real
world situation of software development. The context is
the following : "You have been hired to build and design a
complete multi-platform messaging system just like Skype
or Slack".<br>
<br>
There is of course a part describing the features the
application should have, but also a part describing a
"Support Architecture" of redundant servers and backup
servers.<br>
<br>
It is the opportunity for us to combine our programming as
well as our server managing skills.<br>
<br>
<br>
<b>The question :</b><br>
<br>
So, as I already knew about tox and qTox I suggested we
could use it as a work-base. But what about the server
architecture?<br>
<br>
Therefore, here is our very basic question :<br>
<br>
<i>Can qTox be adapted to fit a server/client
architecture? And if yes, how much work would that
imply?<br>
<br>
</i>We simply wanted the opinion of experts on the matter
so we can decide if it's a viable option before diving
into the specs and actually do the refactoring.<br>
<br>
<br>
Of course we already took a quick look around in the code,
and our feeling currently is that one would only need to
modify the toxcore library for that, leaving the qTox
client unaffected in it's structure. But that arises a
second question : can the toxcore library be easily bended
into a server/client architecture or should we rather make
our own networking library?<br>
<br>
<br>
Thank you very much for your time, and thank you for the
effort you put into tox and qTox.<br>
<br>
Peter Aubry-Walker,<br>
Paul Arcari,<br>
Axel Coche,<br>
Paul Destour,<br>
Loïc Lebon,<br>
Thibault Lemaire,<br>
</div>
<br>
______________________________<wbr>_________________<br>
General mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:General@lists.tox.chat">General@lists.tox.chat</a><br>
<a moz-do-not-send="true"
href="https://lists.tox.chat/listinfo/general"
rel="noreferrer" target="_blank">https://lists.tox.chat/<wbr>listinfo/general</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>