Hi Luis and All, Concerning the specification of requirements, the basic operations expected by the robotics demo Step 1 are those reported in the live demo deliverable at section 4.4.3.1 Step1: Managing interactively robots<https://docs.google.com/document/d/1FMpUKRiX0sDYCONghp0fcuFthF96cw1wQaPx_HKJ7D8/edit#heading=h.f1sfmvbf2hr3> We do agree however that a more refined version is necessary to explain in detail what actions, first of all from a user's (and viewer's as this is a demo) perspective, are to be performed. Perhaps a description similar to the live demo script used in FIWARE I might be helpful. Let's work on this point and come with a refined description of the demo story in a couple of days max. I'll provide asap a link to a shared doc to perform this action. BR Pier Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Luis López Fernández Inviato: martedì 16 giugno 2015 14:15 A: Colombatto Davide Cc: amagan at conwet.com; Javier Soriano; fdelavega at fi.upm.es; fiware-robotics at lists.fi-ware.org; aarranz at fi.upm.es Oggetto: Re: [Fiware-robotics] Robotics GE live demo - Kurento and Wirecloud Hi, In relation to question 1), which is the only one for which I can provide a precise answer: Tutorial 3 is just, as its name indicates, a tutorial, not an application devoted for being used in production. As such, it has a lot of limitations, including the fact that only one master (robot in our case) can be present at any time in the application. Having said this, it shouldn't be too complex to create an application extending tutorial 3 for enabling multiple robots to be broadcasted. We may assume the creation of such an application if you want. However, we would require a short specification of requirements for doing so. For example, a viewer may require to see both robots at the same time? viewers need to register somehow? how we guarantee that master stream comes from a robot? through an authentication mechanism? based on passwords? This types of questions would need to be answered before creating such an application. Best regards. Luis. El 16/06/2015, a las 12:34, Colombatto Davide <davide.colombatto at telecomitalia.it<mailto:davide.colombatto at telecomitalia.it>> escribió: Hi Luis and Wirecloud guys, We have some doubts about the use of Kurento and Wirecloud widgets for Kurento for the Robotics Live Demo. 1) For what concern Kurento, in our past tests we tried the tutorial http://www.kurento.org/docs/current/tutorials/node/tutorial-3-one2many.html where it is said that it can be present only one WebRTC-Master and many WebRTC-Viewers (i.e. it is created a kind of WebRTC-Room where only one can send the video and the others can receive the video). Starting from this point we think the slide2 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 depicts the Kurento One2Many architecture. Considering what mentioned above, if we want to use two different robots (that act as WebRTC-Masters in order to send video) do we need to use two different Kurento Application Servers (that act as Kurento-Clients) or a single Kurento Application Server (that acts as Kurento-Client) is able to manage multiple robots video transmission? 2) For what concern Wirecloud widgets for Kurento, starting from the slide2 at the linkhttps://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3 do the Wirecloud widgets act as Viewer1-UbuntuPC, Viewer2-UbuntuPC, ... of the Kurento One2Many architecture explained above in the point1? If it is correct, for the Robotics live demo will Wirecloud also host the Kurento Application Servers (i.e. a single one or one for each robot that act as WebRTC-Master in order to send video) within the Wirecloud Application Server as depicted in the slide3 at the link https://docs.google.com/presentation/d/110H_bSo6QDOgSX9AYxF8fqB7MAoL6Fb_tcnNtIGnBhk/edit#slide=id.p3? Thank you, Davide Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. <logo Ambiente_foglia2.jpg>Rispetta l'ambiente. Non stampare questa mail se non è necessario. <logo Ambiente_foglia2.jpg> -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20150616/fe1e8381/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy