You don't have to worry about any critical issue that might happen on production. We introduce a feature called peer to peer bypass that allows us to turn off peer to peer in case of an incident. this feature ensures that we can control whether or not our technology is activated on production. We can choose to bypass peer to peer according to the following:
1. Integration platform( Android or IOS)
2. OS version
3. SDK Version
By doing so we ensure to be able to:
- Deactivate new sessions in case a critical issue occurs
This is mostly useful for mobile integrations as the release cycle is longer than the web's release cycle.
- Deprecate a range of old versions we do not want to support anymore
- Ramp-up our different integrations so our customers can manage how much of their traffic they want to have with Streamroot.
The way we check for bypass is by first making a request to the distributor to discover if bypass is activated or not. If bypass is activated then we don't initialize our peer agent and we will act exactly like a proxy which means there will be no cause of any bug from our side.
We try to detect problems before they happen and we will use this feature to bypass peer to peer before any problem takes place. In case you would like to use the bypass feature for different reasons please contact us specifying whether you'd like to bypass our technology on a specific Integration platform, specific OS version or specific SDK version.
To test the activation of our technology:
The easiest way to test the different use cases is to use cURL from your terminal.
$ curl -i https://distributor.streamroot.io/activate\?customer\=dev\&integration\=android\&os_version\=23\&version\=1.4.3
$ curl -i https://distributor.streamroot.io/activate\?customer\=dev\&integration\=ios\&os_version\=11.0\&version\=1.3.2