Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Design & Implementation Issues in a Contemporary Remote Laboratory Architecture

1,244 views

Published on

A short talk given at the Remote Engineering and Virtual Instrumentation 2011 conference in Brasov, Transylvania, Romania June 28-July 1, 2011.

Published in: Education, Technology, Travel
  • Be the first to comment

  • Be the first to like this

Design & Implementation Issues in a Contemporary Remote Laboratory Architecture

  1. 1. Design & Implementation Issues in aContemporary Remote Laboratory Architecture Mark Schulz, CEIT & Adam Rudd, School of ITEE & CEIT The University of Queensland REV2011 Conference, Brasov, Romania
  2. 2. Why undertake this project?Enhance the user experienceProduce open source code REV2011 Conference, Brasov, Romania
  3. 3. Format of TalkReview of iLab ArchitectureIndicate some limitationsPropose some desirable enhancementsLook at some possible implementationissuesVery short demonstration REV2011 Conference, Brasov, Romania
  4. 4. Review of iLab ArchitectureSer vice Oriented Architecture based onWeb ServicesThree major components Ser vice Broker - Authentication & Authorisation, delivery of client LabSer ver - runs the experiment Client - send, receives and displays data REV2011 Conference, Brasov, Romania
  5. 5. Limitations of iLab ArchitectureSERVICE BROKER: Authentication & Authorisation are not a ser vice Client is launched from the SB. REV2011 Conference, Brasov, Romania
  6. 6. REV2011 Conference, Brasov, Romania
  7. 7. REV2011 Conference, Brasov, Romania
  8. 8. REV2011 Conference, Brasov, Romania
  9. 9. Limitations of iLab ArchitectureDevelopment tool chain is (currently)Microsoft centric fragile tool chain shortage of student C# developers at our institution Uses a non-standard Microsoft SQL database REV2011 Conference, Brasov, Romania
  10. 10. Limitations of iLab ArchitectureNo built-in support for real-timemessaging. Some functions generate excessive activity, e.g., to build an experiment progress bar. Others not possible,e.g., to build a real- time job queue viewer REV2011 Conference, Brasov, Romania
  11. 11. Limitations of iLab ArchitectureNo architecture support for distributedcollaboration around the client.Current model is collaboration around asingle remote client - requires physicalpresence.This is NOT about chat sessions andshared whiteboards, although these wouldform part of this approach. REV2011 Conference, Brasov, Romania
  12. 12. Desirable Enhancements to iLab Architecture ‘Rig-as-a-Service’ Client interfaces can be anywhere User needs an account on a trusted ser vice broker to execute the rig, book a session, etc. Moves operation from Service Broker centric to Lab Server centric. REV2011 Conference, Brasov, Romania
  13. 13. Desirable Enhancements to iLab Architecture Real-time, one-to-many messaging Operational Data - progress bar Experiment Data - interactive experiments, sensor experiments Client operational data - button pressed is pushed to all collaborating clients REV2011 Conference, Brasov, Romania
  14. 14. Implementation Issues RESTful interface to replace SOAP Far simpler and more powerful More developers familiar with this now. NOTE: RESTful does not support real-time. No standard for real-time messaging here. REV2011 Conference, Brasov, Romania
  15. 15. Implementation Issues A previous talk today looked at the design of the client in HTML 5, CSS, and JavaScript. Why not reduce the number of languages involved and go for server-side Javascipt (node.js) JS is event-driven cf. SOAP which is RPC. REV2011 Conference, Brasov, Romania
  16. 16. Implementation Issues nodejs.org REV2011 Conference, Brasov, Romania
  17. 17. Implementation Issues If we make the break with SOAP and move to JavaScript, should we follow the trend of other web developers and move totally from XML to JSON? REV2011 Conference, Brasov, Romania
  18. 18. Implementation Issues Real-time Support: Use of websockets Many-to-one messaging Use of Publish/Subscribe protocol (XMPP, MQTT, Redis,?) REV2011 Conference, Brasov, Romania
  19. 19. Short DemonstrationImplemented in JavaScriptUses RESTful interfaceUses websockets via socket.io forbackwards compatibilityReplaced the Time-of-Day with a Twitter-feed filterNo authentication & authorization REV2011 Conference, Brasov, Romania
  20. 20. Thank You & Comments/REV2011 Conference, Brasov, Romania

×