From thibault.lemaire at supinfo.com Thu Mar 9 19:27:17 2017 From: thibault.lemaire at supinfo.com (Thibault Lemaire) Date: Thu, 9 Mar 2017 20:27:17 +0100 Subject: [General] School project using qTox Message-ID: <41f302ff-41f5-0e63-f9d8-dd840379c1be@supinfo.com> Hello, 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. *About the project :* 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". 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. It is the opportunity for us to combine our programming as well as our server managing skills. *The question :* 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? Therefore, here is our very basic question : /Can qTox be adapted to fit a server/client architecture? And if yes, how much work would that imply? /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. 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? Thank you very much for your time, and thank you for the effort you put into tox and qTox. Peter Aubry-Walker, Paul Arcari, Axel Coche, Paul Destour, Lo?c Lebon, Thibault Lemaire, -------------- next part -------------- An HTML attachment was scrubbed... URL: From email at oranges.net.nz Thu Mar 9 20:09:13 2017 From: email at oranges.net.nz (Oranges User) Date: Fri, 10 Mar 2017 09:09:13 +1300 Subject: [General] School project using qTox In-Reply-To: <41f302ff-41f5-0e63-f9d8-dd840379c1be@supinfo.com> References: <41f302ff-41f5-0e63-f9d8-dd840379c1be@supinfo.com> Message-ID: 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. On Fri, Mar 10, 2017 at 8:27 AM, Thibault Lemaire < thibault.lemaire at supinfo.com> wrote: > Hello, > > 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. > > > *About the project :* > > 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". > > 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. > > It is the opportunity for us to combine our programming as well as our > server managing skills. > > > *The question :* > > 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? > > Therefore, here is our very basic question : > > > > *Can qTox be adapted to fit a server/client architecture? And if yes, how > much work would that imply? *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. > > > 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? > > > Thank you very much for your time, and thank you for the effort you put > into tox and qTox. > > Peter Aubry-Walker, > Paul Arcari, > Axel Coche, > Paul Destour, > Lo?c Lebon, > Thibault Lemaire, > > _______________________________________________ > General mailing list > General at lists.tox.chat > https://lists.tox.chat/listinfo/general > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amuza at riseup.net Fri Mar 10 11:04:08 2017 From: amuza at riseup.net (Amuza) Date: Fri, 10 Mar 2017 12:04:08 +0100 Subject: [General] School project using qTox In-Reply-To: References: <41f302ff-41f5-0e63-f9d8-dd840379c1be@supinfo.com> Message-ID: <58C28828.6050404@riseup.net> > > 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. > = ) > 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. > > > /Can qTox be adapted to fit a server/client architecture? And if > yes, how much work would that imply? > > / > Client-server architecture? That sounds like contributing to the problem. Is there any chance that that project could be redirected so that it contributes to the solution? I mean it would be nice to have 6 more people helping to have a more decentralized world by somehow improving Tox -or any other Free Software going in that direction. I'm not a Tox expert, but I think every Tox node can be seen as a client and a redundant server itself. For the backup thing, maybe you want to consider to implement a distributed solution instead of a centralized one. > > Thank you very much for your time, and thank you for the effort > you put into tox and qTox. > > Peter Aubry-Walker, > Paul Arcari, > Axel Coche, > Paul Destour, > Lo?c Lebon, > Thibault Lemaire, > > _______________________________________________ > General mailing list > General at lists.tox.chat > https://lists.tox.chat/listinfo/general > > > > > > _______________________________________________ > General mailing list > General at lists.tox.chat > https://lists.tox.chat/listinfo/general -------------- next part -------------- An HTML attachment was scrubbed... URL: From thibault.lemaire at supinfo.com Wed Mar 15 15:31:53 2017 From: thibault.lemaire at supinfo.com (Thibault Lemaire) Date: Wed, 15 Mar 2017 16:31:53 +0100 Subject: [General] School project using qTox In-Reply-To: References: <41f302ff-41f5-0e63-f9d8-dd840379c1be@supinfo.com> Message-ID: Alright thank you all for your replies. 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. Thanks again and keep up the good work! On 09/03/17 21:09, Oranges User wrote: > 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. > > On Fri, Mar 10, 2017 at 8:27 AM, Thibault Lemaire > > > wrote: > > Hello, > > 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. > > > *About the project :* > > 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". > > 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. > > It is the opportunity for us to combine our programming as well as > our server managing skills. > > > *The question :* > > 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? > > Therefore, here is our very basic question : > > /Can qTox be adapted to fit a server/client architecture? And if > yes, how much work would that imply? > > /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. > > > 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? > > > Thank you very much for your time, and thank you for the effort > you put into tox and qTox. > > Peter Aubry-Walker, > Paul Arcari, > Axel Coche, > Paul Destour, > Lo?c Lebon, > Thibault Lemaire, > > _______________________________________________ > General mailing list > General at lists.tox.chat > https://lists.tox.chat/listinfo/general > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: