IoT with SignalR & .NET Gadgeteer - NetMF@Work

NetMF@Work
NetMF@Work
IoT with SignalR & .NET Gadgeteer
Mirco Vanini
http://mircovanini.blogspot.com
info@proxsoft.it
@MircoVanini
Microsoft MVP Windows Embedded

NetMF@Work
Perché real-time e come ?
SignalR
Connections and Hubs
Clients
Demo
Q&A
Links
Agenda

NetMF@Work
Gli utenti vogliono le ultime informazioni, ORA !
Twitter – live searches/updates
Stock streamers
Auctions
Live scores
Real-time notifications
Interactive games
Collaborative apps
Live user analytics
.

NetMF@Work
HTTP is an old beast…
Never designed for real-time communications
Web is request-response
Web is stateless
HTML5 WebSockets to the rescue, right?
Extension to HTTP
Provide raw sockets
over HTTP
Full-duplex
Traverses proxies
It’s still a draft…
Not every proxy server supports it
Not every webserver supports it
Not every browser supports it
They are raw sockets!
 

NetMF@Work
Come implementare il real-time con HTTP:
• Polling.
• Long Polling.
• Forever Frame.
• Server Sent Events

NetMF@WorkPerché real-time e come ?
Polling: the stubborn approach
Server
Client
Time: requests event ‘n’ seconds (fixed time)
Request
Response
delay
Twitter clients

NetMF@Work
Polling
• High overhead on requests: headers and
such…
• High overhead on response: same as before…
• High latency.
• Waste of bandwith.
• Waste of resources.

Long Polling: the kind gentleman approach
Server
Client
Time: requests event ‘n’ seconds (variable)
Request
Response
Variable delay
Facebook chat

NetMF@Work
Long Polling (Hanging GET)
• High overhead on requests: headers and
such…
• High overhead on response: same as before…
• Medium latency.
• Waste less of bandwith.
• Waste of resources.
• Better than the previous one: less requests

HTTP/1.1 200 OK
Content-Type: text/plain
Transfer-Encoding: chunked
• Server tells client that response is chuncked
• Client keeps connection open untill server closes it
• Server pushes data to the client followed by 0
• Consumes server threads
<script>eval("... ")</script>0
<script>eval("... ")</script>0
Forever Frame

NetMF@Work
Server-Sent Events
• Server-Sent Events (SSE) are a standard describing
how servers can initiate data transmission towards
clients once an initial client connection has been
established. They are commonly used to send message
updates or continuous data streams to a browser client
and designed to enhance native, cross-browser
streaming through a JavaScript API called EventSource,
through which a client requests a particular URL in order
to receive an event stream.
Stream Updates with Server-Sent Events

NetMF@Work
So many options and a big Headache !
Real-time: How to survive ?

NetMF@Work
• Persistent Connection Abstraction communication
library.
• Abstracts protocol and transfer (choses the best one).
• A single programming model (a unified development
experience).
• Extremely simple to use.
• Server-side it can be hosted in different «environments»
(ASP.NET, console apps, windows services, etc…).
• Client-side there’s support for: Javascript clients, .NET
clients, WP; provide by the community: iOS, Android.
SignalR

NetMF@Work
• Works everywhere !!!
• Try WebSocket then fallback to:
• Server Sent Events
• Forever Frame
• Long Polling
• Bet to keep the logic connection up include retry
logic
• Scale out to web-farms
SignalR

NetMF@Work
• Complete rewrite of the internals for 1.0.0
• Very hight performance on a single box
100.000’s of messages per seconds
• Very low memory overhead
• Full async
• 1000’s of connection per server
• Cross-platform: run it on OSX or Linux with
Mono
• Supported part of ASP.NET family
SignalR

NetMF@Work
Persistent Connections: «Low level» API,
manages the connection and the «raw» stream of
data.
Hubs: «High level» API, provide advanced support
for internal routing (calling functions on server &
clients), connection and disconnection tracking,
grouping etc… Automatic client proxy generation
(JavaScript)
SignalR

NetMF@WorkSignalR
Install-Package Microsoft.AspNet.SignalR –pre
Install-Package Microsoft.AspNet.SignalR.Sample -
pre

NetMF@Work
Core
• Microsoft.AspNet.SignalR.Core: Server side components needed to
build SignalR endpoints
Meta package
• Microsoft.AspNet.SignalR: - A meta package that brings in everything
you need to run it on IIS and ASP.NET
Hosts
• Microsoft.AspNet.SignalR.SystemWeb - Pulls in the required
packages to host SignalR in ASP.NET (via OWIN ASP.NET host)
• Microsoft.AspNet.SignalR.Owin - OWIN* host for SignalR
* OWIN stands for “Open Web Interface for .NET” and it is a specification for
the communication between .NET Web Server and Web applications.
SignalR packages

NetMF@Work
Clients
• Microsoft.AspNet.SignalR.Js - Javascript client for SignalR
• Microsoft.AspNet.SignalR.Client - .NET client for SignalR (includes
WinRT, Windows Phone 8 and Silverlight5 clients)
Scaleout Buses
• Microsoft.AspNet.SignalR.Redis - Redis scaleout for SignalR
• Microsoft.AspNet.SignalR.ServiceBus - Service bus scaleout for
SignalR
Sample
• Microsoft.AspNet.SignalR.Sample - A sample stock ticker you can
quickly and easily bring into your app to get a working sample up and
running.
SignalR packages

NetMF@Work
Web Plant Monitor
PlantHub
PlantMonitor
PlantManager
Plant Device
PlantCommand
PlantData
TcpCommandListener
Demo

NetMF@Work
Page
Page
Schema
HUB Device
Page
SendCommand
data
command
22000
21000
data
updatePlaintData
command

NetMF@Work
ASP.NET SignalR
Building Real-time Web Apps with ASP.NET SignalR
Engaging the Realtime Web with SignalR
SignalR. Code, not toothpaste.
Links

NetMF@WorkFeedback Form
Per voi sono solo 10 minuti persi, per
noi è utilissimo per poter crescere!!!!
http://tinyurl.com/netmfwork

IoT with SignalR & .NET Gadgeteer - NetMF@Work

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a IoT with SignalR & .NET Gadgeteer - NetMF@Work

Semelhante a IoT with SignalR & .NET Gadgeteer - NetMF@Work (20)

Mais de Mirco Vanini

Mais de Mirco Vanini (20)

Último

Último (20)

IoT with SignalR & .NET Gadgeteer - NetMF@Work