We've had an answer from Luis to the e-mail from Davide concerning the set of questions for Kurento (which were part of the questions below). Luis asked further question and details about the demo. After that Pier has sent an e-mail to Luis and all the Robotics group to suggest working on a document to better describe step by step what we want to show in the Live demo. We are working now on this new document and will share a version of it by tomorrow; according to the suggestion from Pier, we can first refine this document and then we will be able to forward our questions to Wirecloud and Kurento, providing them with a more detailed description of what we want to show and we'll need for the Live demo. Best, Gianmario Da: fiware-robotics-bounces at lists.fi-ware.org [mailto:fiware-robotics-bounces at lists.fi-ware.org] Per conto di Jose Jaime Ariza Inviato: martedì 16 giugno 2015 17:22 A: fiware-robotics at lists.fi-ware.org Oggetto: Re: [Fiware-robotics] Proposal of Q to Kurento and Wirecloud Hi, I think they're ok. I'd just change "demo have few questions" by "demo and have a few questions". BR, Pepe. On 16/06/15 12:38, Bollano Gianmario wrote: Dear all, we are defining further details for the Robotics Live demo. Robotics Live demos consist of transmitting video from robots camera, controlling the robots with a Joystick from a Web interface, displaying robot status, their positioning, and their video stream. We are defining the architecture for the Robotics demo have few questions and hypothesis we need to check with you: 1. To use widgets to control Robots and displaying video from robots, can we use the public instance of Wirecloud in FIWARE LAB [our Hypothesis] or do we need to instantiate a dedicated Wirecloud instance (reserved only for Robotics demo in a specific VM)? 2. Will we be able to run different widgets in the same Wirecloud instance for different functions [our Hypothesis], e.g. to control the robot with a Joystick interface, to Initialize Robots configuration (that means writing few information using APIs to configure Robot environment), to display Robot positioning and data? 3. If we have 2 robots to transmitting Video streams, will we need two Application servers (one per stream), or just one [our Hypothesis]? Can we use the same Application server for video TX and RX endpoints [our Hypothesis]? 4. If we want to use a Kurento Widget in Wirecloud, can we assume that the Application server (to host Kurento client) is the same one embedded in Wirecloud [our Hypothesis] or do we need an external Application server? To manage two video streams transmitted by two robots, do we need two widgets? Can these widget use the same Application server? Best, Gianmmario ------------------------------------------------------------------------------------ Telecom Italia Gianmario Bollano Innovation - Mobile Devices & Sim Applications Via Reiss Romoli, n° 274 Cap 10151 Torino Phone 011 228 7103 Cell Phone 3316015048 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. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario. -- José Jaime Ariza R&D Engineer +34 696604288 Ikergune, Etxe-Tar group -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-robotics/attachments/20150616/cd6abb04/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy