From 53c94b9450f41e6be964398c55d33efdd0633bf9 Mon Sep 17 00:00:00 2001 From: David Fowler Date: Thu, 15 Jun 2017 09:22:14 +0200 Subject: [PATCH] Updated the spec - Removed the text and binary frames distinction - Removed the datagram requirement --- specs/HubProtocol.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/specs/HubProtocol.md b/specs/HubProtocol.md index 06161ff2e5..7797f855f7 100644 --- a/specs/HubProtocol.md +++ b/specs/HubProtocol.md @@ -12,8 +12,6 @@ The SignalR Protocol is a protocol for two-way RPC over any Message-based transp The SignalR Protocol requires the following attributes from the underlying transport. The protocol was primarily designed for use with WebSockets, though it is relatively straightforward to build an adaptor layer for a different transport. -* Message-based (aka Datagram, as opposed to Streaming) -* A distinction between Text and Binary frames * Reliable, in-order, delivery of messages - Specifically, the SignalR protocol provides no facility for retransmission or reordering of messages. If that is important to an application scenario, the application must either use a transport that guarantees it (i.e. TCP) or provide their own system for managing message order. ## Overview