AllJoyn: Building Universal Windows Apps that Discover, Connect, and Interact with Other Devices and Cloud Services Using AllJoyn

Download this episode

Download Video

Download captions

Download Captions

Description

Microsoft joined the AllSeen Alliance in mid-2014 and is deploying AllJoyn technology into Windows 10 as the device connectivity platform for Internet of Things (IoT), consumer, and enterprise devices.  AllJoyn is an open source framework that enables companies and individuals to create interoperable products that can discover, connect and interact with other devices and cloud services regardless of manufacturer, vertical or network.  In this session you will learn the value of adding AllJoyn into your devices to unlock the power of IoT interoperability.  We will demonstrate how easy it is to write a Windows app to command/control AllJoyn devices.

Day:

1

Session Type:

Code Lab

Code:

2-623

Room:

Room 3018

Embed

Format

Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • User profile image
      bendyson

      Can we expect to see a recording for this session uploaded?

    • User profile image
      salemsalah

      رائئعة  

    • User profile image
      TheEveryman

      Here is the link to the blog post they were mentioning.

      Step-By-Step: Building AllJoyn Universal Windows Apps for Windows 10 Public Preview

      IoT Blog

    • User profile image
      chrislesage

      I dont necessaraly see the need for all these wrapping layers. At the Belgian Railways we implemented the same infrastructure over devices with only Masstransit, RabbitMq and some easy to manage and version interfaces. It was the biggest project in Belgium (over 15.5 mil euro, with spin off's amounting to almost 200 milj euro).. Every kind of device conncected with a Windows 8.1 hub device and numerous satellite devices.

      The messaging pattern style we used was a lot simpler, only consisting of:

      - Command (like the actions here)

      - Events (things that didn't needed actions or responses)

      - Request/Response messages (asynchronously)

      We are even going to repeat this success with the Electricity market..

      :)

       Instead of adding/removing events on watchers we used prism's framework EventAggregator since it was more robust to errors/memory-leaks or missing event removals -= 

      I will certainly look deeper into the Alljoyn frameworks and methodologies, if only because they might use something I didn't think of. It only seems a lot of overhead, no?

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.