5.0 Documentation


PureWeb SDK 5.0 Release Notes

These Release Notes apply to all 5.0.x releases of the PureWeb SDK.

New in PureWeb 5.0

  • Improved H.264 support.
  • Added support for recent versions of platforms and tools:
    • RHEL 7, Windows 10, Windows Server 2016
    • Visual Studio 2017
    • OpenJDK 11
  • Enhanced security: The versions of Tomcat, Spring Framework and Spring Security used by the PureWeb server have been updated, to ensure that they are up-to-date with the latest security patches.
  • SDK compatibility with our fully managed scalable cloud offering.


  • Default process (deprecated since 4.1)

    The default process mechanism is deprecated. This mechanism allows for instances of the specified process to be automatically started by the PureWeb server in all available user sessions.


  • The clustering mechanism, which was deprecated since 4.0, has now been officially discontinued. Multi-server environments must be scaled using load balancers.
  • The Flex client SDK was deprecated in 4.1, and has now been officially discontinued. The SDK is not included with the 5.0 release.
  • We are no longer offering the following SDKs: Java SDK for service-side development, and Android and iOS SDKs for development of client-side native mobile apps.
  • The following platforms are no longer supported (see the Requirements for a list of currently supported versions):
    • Windows 7, Windows 8.1, Windows Server 2008 R2, Windows Server 2012 R2 Update
    • RHEL 6.x and Ubuntu
    • Visual Studio 2008 and 2010, and 32-bit applications on Windows
    • gcc 4 on Linux
    • Oracle JRE
  • Passwords are no longer encrypted using SHA-1. The Bcrypt algorithm is now used instead.

See also the Upgrade notes for details on what's changed at the API level.

Known issues and recommendations

The following issues have been identified as expected behavior, or are due to limitations in a third-party application:

  • There is a memory leak when reloading the system from the configuration page as described under General configuration. To avoid this leak, we recommend restarting the server instead, as described in Starting and stopping the server. (PWEB-7445)
  • When running a client application in multiple windows, some extensions for the Google Chrome browser could interfere and cause the application to crash, If this happen, disable the extension in the browser. (PWEB-6813)
  • HTML5 client logging — browser-specific peculiarities (PWEB‑3532)

    The PureWeb HTML5 client SDK performs a degree of internal logging. By design, developers creating PureWeb client applications see only the messages logged when there is an unexpected operation within the PureWeb SDK, while the low-level messages logged under normal operation are not visible to them.

    The visible messages are normally logged to the JavaScript console in the browser, but developers should be aware of the following peculiarities that have been found to exist in some versions of the browsers:

    • Firebug: the logging messages will not appear in the Firebug console, but rather will be sent to the default JavaScript console in Firefox.
    • Google Chrome: When using multiple user profiles within Google Chrome, logging messages will only appear in the window of the first profile that was accessed. This issue is not present when using only the default profile.