PureWeb 4.3 Release Notes
These Release Notes apply to all 4.3.x releases of the PureWeb SDK.
Corrections and Modifications:
- Fixed memory leaks when running the HTML5 client in Internet Explorer 11. (PWEB-6951)
- When running an HTML5 client in Internet Explorer 11, the mouse wheel direction was interpreted opposite to that of other browsers. (PWEB-6952)
- Fixed a recently introduced library dependency issue that would cause errors when using PureWeb with Visual Studio 2008. (PWEB-6954)
- The PureWeb server now uses a versionless schema for Spring. (PWEB-6974)
- Use of the defaultProcess mechanism would sometimes generate duplicate logs. (PWEB-6994)
Corrections and Modifications:
- Changes to the service-side libraries:
- The versions of the ICU library (for Unicode support) and libjpeg-turbo library (for JPEG compression) have been upgraded, to ensure that they are up-to-date with the latest security patches. (PWEB-6812, PWEB-6780)
Fixed a potential array index out-of-bounds issue. (PWEB-6788)
- Fixed various potential integer overflow issues. (PWEB-6789 to PWEB-6798)
- Changes to the HTML5 client API:
Added an optional focusAfterCreate parameter to the View constructor, which can be used to prevent the view from automatically grabbing focus when created. Input events are not captured when a view is not in focus. (PWEB-6879)
This is the initial release of version 4.3. See New in PureWeb 4.3 further down on this page for the list of new features and enhancements.
This release also addresses the following:
- When running an HTML5 client in multiple windows in Internet Explorer, sometimes cross-window messaging would cause the browser to stall. (PWEB-6536)
- Code modifications were made to correct cross-site scripting (XSS) vulnerabilities; in particular to prevent error messages from exposing non-generic information. (PWEB-6547)
Changed the value of the KeepAliveTimer in the iOS API to 5 seconds, to make it consistent with the other client APIs. (PWEB-6356 and PWEB-6473)
- Enhanced security: The versions of JQuery, logback, Tomcat, Spring Framework and Spring Security used by the PureWeb server have been upgraded, to ensure that they are up-to-date with the latest security patches.
- Enhancements to the APIs:
- C++: A new method has been added to the API, to simplify string conversions. The method, ToStdUtf8, can be found in the String class. For more information, see String Conversions in C++.
- iOS: The API libraries and the sample applications now support iOS 10, Xcode 8, Swift 3 and .CocoaPods 1.1.x.
- HTML5: A new method has been added to facilitate the cleanup of views once they are not needed anymore. For more information, see the documentation for the view.dispose() method.
- Flex: The API libraries and the sample applications now support Flex 4.15.
- Enhancements to the sample applications: All the samples now include performance metrics (encoder format, latency, bandwidth, and frames per second).
- Enhancements to the documentation: The developer documentation underwent a complete overhaul, to improve the content structure and simplify navigation.
Known Issues and Recommendations
The following issues have been identified as expected behavior, or are due to limitations in a third-party application:
- 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).
- Flex clients sometimes do not work in the Microsoft Edge browser: either they do not load properly, or they load but do not connect to the PureWeb server. (PWEB-6626)
Workaround is to close and restart the Edge browser and/or restart the PureWeb server.
- Flash clients may exhibit poor performance when running in Firefox on Windows 7. (PWEB‑4345)
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.
- 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.
The following features are deprecated:
- 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.
Flex Client SDK (deprecated since 4.1)
If you are currently using a Flex client, we recommend that you migrate to one of the other supported clients (HTML5, iOS, Android).
- Clustering (deprecated since 4.0)
While the current clustering mechanism is still supported for small multi-server environments (2 to 3 servers), it is recommended that a load balancer be used for such environments instead.
A solution to improve management and scalability of multi-server environments is currently being developed for a future release of PureWeb.
For details on deprecated API methods, refer to the Upgrade Notes.
- The Java Swing client SDK was deprecated in 4.0, and has now been officially discontinued. The SDK is not included with the 4.3 release.
- The following platforms/browsers are no longer supported:
HTML5: Firefox ESR
- iOS: Xcode 7, iOS 8 and Swift 2.x, and versions of Cocoapods below 1.1
- Android: Versions of Android below 5.x, API levels below 21, and versions of Android Studio below 2.x
- Ubuntu 12.04 LTS and Mac OS X 10.10
See the Requirements for a list of currently supported versions.