[Fiware-miwi] Recent Meshmoon developments with FIWARE MIWI GEs at Adminotech

[Jonne Nauha]

Hello everyone,

MIWI just got its January release out the door. I'd like to take the
opportunity to update everyone how we at Adminotech are using FIWARE GEs in
our products and services.

We did a big update to the Meshmoon platform today. We published the public
WebRocket 1.0 web client today and updated realXtend Tundra based Meshmoon
Rocket clients and our servers to 2.5.3.0. Our website also got a facelift
and usability improvements.

*WebRocket 1.0*

As said the public WebRocket 1.0 is out now. Please visit and test it at
www.meshmoon.com, sign in and head over to the WebRocket page from the top
bar. Select a world and login. Latest Chrome or Firefox browser are
supported/recommended.

Here is WebRocket in action
https://dl.dropboxusercontent.com/u/3589544/meshmoon/fiware/meshmoon-webrocket.png.
Connected to one of our partners, Oulu3D, Church of Haukipudas world where
an actual church near by here in Oulu Finland was modeled as a virtual
Meshmoon world. Its one of the three scenes we are launching WebRocket
with, but more is to come!

   - *FIWARE.OpenSpecification.MiWi.2D-UI
   <http://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.MiWi.2D-UI>*
(Adminotech)
   The GE implementation was based on our earlier InputAPI and UiAPI from
   WebRocket development, which we took further during FIWARE development.
   Both APIs are part of the WebRocket 1.0 core.
   - FIWARE.OpenSpecification.MiWi.InterfaceDesigner<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.MiWi.InterfaceDesigner>
(Adminotech)
   This GE is fully integrated to manipulate the scene in WebRocket 1.0. The
   editor application is hidden if you are not a admin in the world. Our
   server logic will ignore scene modification from users that dont have
   permission to modify that particular world, but its always good to hide the
   UI app on the client side when we know you don't have permissions, not just
   to fail later.
   - FIWARE.OpenSpecification.MiWi.Synchronization<http://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.MiWi.Synchronization>
(Ludocraft)
   We have our own web browser side javascript implementation of the Tundra
   protocol synchronization. So essentially we are not using the GEi
   Lasse/Ludocraft made, but we have implemented our own GEi as per the
   Synchronization GE spec. Meaning that we have at least two client side
   implementations of this GE out in the world :)

*Meshmoon Server 2.5.3.0*

   - *FIWARE.OpenSpecification.MiWi.Synchronization
   <http://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.MiWi.Synchronization>
*(Ludocraft)
   We open sourced our Meshmoon web socket server implementation after the
   start of the project, which got merged to realXtend Tundra. Lasse continued
   great work from the initial push, updating the server to use the latest
   stable release of the C++ library we use for web socket networking. Another
   significant effort there was to modify the whole realXtend Tundra core to
   allow multiple network protocols to be enabled at the same time. Normally
   we used only UDP or TCP to allow user connections, now both those and web
   socket connections work at the same time. Modifying the core aspects of
   Tundra networking to allow flexible sub classing with different network
   protocols and making all of the "first class citizens" and basically making
   transparent to the 3rd party code handling those user connections what the
   underlying protocol is. This was a monumental help for us and the open
   source WebSocketServerModule<https://github.com/realXtend/tundra/tree/tundra2/src/Application/WebSocketServerModule>
is
   a part of both the Meshmoon Rocket client and the Meshmoon Server. A stable
   WebRocket 1.0 release would have not been possible without us adopting the
   Synchronization GE to our products and Ludocrafts continuation work.

*Meshmoon Rocket 2.5.3.0*

Cloud Rendering GEi in action
https://dl.dropboxusercontent.com/u/3589544/meshmoon/fiware/adminotech-cloud-rendering.png.
Shows the web service in the top right corner, facilitating the initial
signaling to connect web clients with a renderer instance. At the bottom
right corner the Meshmoon Rocket client acting as a cloud renderer,
registered to the web service. On the left you can find the browser web
client that has received a renderer from the web service and connected to
it for WebRTC based video streaming. The client can control the renderer
with mouse and keyboard input (using the video element as it was the actual
client).

   -
*FIWARE.OpenSpecification.MiWi.Synchronization
   <http://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.MiWi.Synchronization>
(Ludocraft) To
   continue on the above test: The Tundra plugin is also a part of our client
   distribution so that our end users/developers can run Tundra servers
   locally with web client support. Once we package a WebRocket 1.0 SDK this
   will become reality. So devs have a full development stack at their
   disposal when they install our client. *
   - *FIWARE.OpenSpecification.MiWi.CloudRendering
   <http://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/FIWARE.OpenSpecification.MiWi.CloudRendering>
(Adminotech)
   The Cloud Rendering renderer Tundra plugin is shipped to all our end users
   in the 2.5.3.0 client. It is not loaded by default, but in practice anyone
   can register their own renderer to a Cloud Rendering GEi web service and
   start playing around with it. We were initially interested in participating
   in the Cloud Rendering GE because we saw real business cases for it. The
   initial release is out and shows everyone a working setup streaming server
   side rendering via WebRTC video to web browser clients. The reference GEi
   is not production quality yet, but with some performance optimization on
   the Tundra rendering side and making the service more user friendly we see
   that will utilize this GE in the Meshmoon ecosystem. As per the intent of
   the GE to provide low perf mobile devices with server side rendering of any
   application, but we also see other use cases for server side rendering.*


Thanks to everyone in the MIWI project for the good cooperation and good
first push for the January release! Feel free to forward the email to any
parties you think might be interested.

Best regards,
Jonne Nauha
Meshmoon developer at Adminotech Ltd.
www.meshmoon.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20140130/4aa8847a/attachment.html>