5.5.0 HTML SDK release.

src/webapps/live/lib/red5pro/CHANGES.md

@@ -1,5 +1,17 @@
 # Changes
 
+## 5.5.0
+
+- default to srcObject in try...catch for modern browsers. (bustardcelly)
+- fix for bandwidth inject in latest chrome browser. (bustardcelly)
+- adding notification and retry support for autoplay restriction of subscribers. (bustardcelly)
+
+    > * WebRTC, RTMP and HLS Subscriber support
+    > * muteOnAutoplayRestriction configuration property added
+    > * Additional subscriber events for client-side notifications of autoplay restrictions
+
+- allowing for decoupled socket for sharedobject connections. (bustardcelly)
+
 ## 5.4.0
 
 - screenfull dep update. (bustardcelly)

src/webapps/live/lib/red5pro/MIGRATION_GUIDE.md

@@ -2,10 +2,25 @@
 
 This documentation serves as a guide in migrating client-side code where a breaking change to the API has been made in a distribution.
 
+* [5.4.0 to 5.5.0](#migrating-from-540-to-550)
 * [5.0.0 to 5.4.0](#migrating-from-500-to-540)
 * [4.0.0 to 5.0.0](#migrating-from-400-to-500)
 * [3.5.0 to 4.0.0](#migrating-from-350-to-400)
 
+# Migrating from `5.4.0` to `5.5.0`
+
+The `5.5.0` release of the Red5 Pro HTML SDK including some modifications to `SharedObjects` to allow for "decoupling" the managament and communication API from the underlying connections for Publishers and Subscribers. In the `5.5.0` release, `SharedObjects` can now be used by themselves without requiring an already established connection to the server.
+
+* The `SharedObject` API has been decoupled from requiring previously established stream clients (Publisher and/or Subscriber).
+  * By decoupling the previous *requirement* to use a established stream client, `SharedObjects` can now be used with establishing a  `WebSocket` connection and providing that as the connection to communicate over `SharedObjects`.
+  * The Red5 Pro HTML SDK provides a `Red5ProSharedObjectSocket` class to serve as a proxy to an underlying `WebSocket` and convenience in communicating to and from the Red5 Pro Server when using `SharedObjects`.
+  * The `SharedObject` API can still be employed using a stream client connection as was possible in previous SDK versions.
+
+Additionally, notification support for latest browser vendor restictions on the `autoplay` policy have been included.
+
+* Utilize the `muteOnAutoplayRestriction` initialization configuration property for Subscriber clients in order to attempt auto-muting of subscribers to allow - at least - video auto-playback when browsers enforce the muted autoplay policy.
+* Listen for events related to `autoplay` restictions in order to provide a better User Experience for your customers.
+
 # Migrating from `5.0.0` to `5.4.0`
 
 The `5.4.0` release of the Red5 Pro HTML SDK saw some minor changes related to WebRTC clients, and in particular how WebSoskcet and RTCPeerConnections are made:
@@ -15,10 +30,6 @@ The `5.4.0` release of the Red5 Pro HTML SDK saw some minor changes related to W
   * To support backward compatiibilty for webapps out in the wild, the HTML SDK will recognize previously defaulted values and silently change the values to new default values.
 * The `iceServers` configuration property has been deprecated in favor of the new `rtcConfiguration` configuration property.
   * [Refer to section: RTCConfiguration](#rtcconfiguration)
-* The `SharedObject` API has been decoupled from requiring previously established stream clients (Publisher and/or Subscriber).
-  * By decoupling the previous *requirement* to use a established stream client, `SharedObjects` can now be used with establishing a  `WebSocket` connection and providing that as the connection to communicate over `SharedObjects`.
-  * The Red5 Pro HTML SDK provides a `Red5ProSharedObjectSocket` class to serve as a proxy to an underlying `WebSocket` and convenience in communicating to and from the Red5 Pro Server when using `SharedObjects`.
-  * The `SharedObject` API can still be employed using a stream client connection as was possible in previous SDK versions.
 
 ## RTCConfiguration