Release Notes

PureWeb® STK 4.x

Calgary Scientific Inc. 2013

Contents

Introduction
Known Issues and Recommendations
Discontinued and Deprecated Support
Additional Information

Links to Specific Releases

4.0.0 [2013/07/30] – Initial Release

Introduction

These Release Notes apply to all 4.x releases of the PureWeb STK (software transformation kit). Information will be added to this document as subsequent versions are released. 

The Known Issues and Recommendations section is a cumulative list with the most recent items at the top of the list. This list includes information on when individual items were found.

The Discontinued and Deprecated Support section is also a cumulative list with the most recent items at the top of the list. This list includes functionality that is no longer supported, and the release number of the version in which support was discontinued. It also contains a list of deprecated items that are still supported but will be discontinued in an upcoming release.

Top of Page


Release Number 4.0.0 [2013/07/30] – Initial Release

New in This Release
Supported Operating Systems
Supported Browsers for HTML5 Clients

Corrections and Modifications

New in This Release

This section describes new features that were introduced in the initial 4.0 release of PureWeb STK.


Supported Operating Systems

Although only 64-bit platforms are supported for application development, the applications developed using the PureWeb STK can be targeted for deployment on 32-bit or 64-bit platforms.

Microsoft Windows

The following versions of Microsoft Windows are supported for running the PureWeb server, C++, C# (.NET), and Java service development, and HTML5, Microsoft Silverlight, Adobe Flex, Java Swing and Android client development.

Linux

The following versions of Linux are supported for running the PureWeb server, C++ service development, and HTML5 and Adobe Flex client development.

iOS

The following versions of Mac OS X are supported for iOS client development.


Supported Browsers for HTML5 Clients

The PureWeb HTML5 Client STK uses the following HTML5 features:

Because the level of support for these features varies across browsers, we recommend using one of the following. These browsers support all the above features, have been tested for use with PureWeb HTML5 clients, and offer optimal performance:

Note that Internet Explorer is only supported when running in Standards Mode (i.e., Compatibility Mode must be disabled). To ensure that Internet Explorer runs in this mode, the following declaration should be included at the beginning of the html file of your PureWeb HTML5 client: <!DOCTYPE html>

Other browsers/versions may be supported by clients developed using the PureWeb HTML5 client STK. For browsers that do not support all the necessary HTML5 features, such as Safari 6.0 and Mobile Safari 6.0, PureWeb will attempt to fall back to alternate mechanisms that are supported by a wider browser base.

Note: Memory bloat issues have been observed in some cases for browsers other than Chrome. We are working with the relevant parties to have these issues resolved.


Corrections and Modifications

There are no corrections or modifications in the initial release of PureWeb 4.0.

Top of Page


Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this product.


Share buttons in PureWeb sample applications do not work in Internet Explorer 10 when running in the Windows 8 style UI (Issue# PWEB-3635).

This is because the Share buttons in the PureWeb samples user the JavaScript prompt() functionality, which Internet Explorer 10 does not support when running in the Windows 8 style UI ("metro mode").

Users developing applications targeted for Windows 8 are encouraged to not use prompt().

Workaround:

Users of the PureWeb sample client applications in Windows 8 can change the operating system's UI to the traditional desktop mode, where the Share buttons will work correctly.

Found In:  4.0.0

HTML5 client logging - browser-specific peculiarities (Issue# PWEB-3532).

The PureWeb HTML5 client STK 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 STK, 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:
  1. Firebug: the logging messages will not appear in the Firebug console, but rather will be sent to the default JavaScript console in Firefox.
  2. 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.
Found In:  4.0.0

When running an HTML5 client in a Chrome browser on Android 4.x, the client application does not disconnect when the user closes the tab (Issue# PWEB-3499).

This is because the Chrome browser on Android does not trigger an onunload or an onbeforeunload event when the user closes the browser tab.

Developers need these events to automatically disconnect the Android client. The issue is not noticeable to the end users, unless they try to reconnect to the client before the server has cleaned the orphaned session created when the tab was closed (by default, the server cleans up the processes every 30 seconds). In this case, they would see an error message. Note that this issue only occurs when the user attempts to disconnect by closing the tab in Chrome. If the client application provides another means to disconnect, such as a Log Off button that calls pureweb.disconnect(true), this issue will not arise if the user terminates the session using this method instead.

Workaround:

To minimize the likelihood that the user will see the error message when they try to reconnect to the client after closing the tab, set up the server to clean up orphaned processes more frequently. To do this, change the value of the process.shutdown.timeout property in the cluster-plugin.properties file. Instructions for changing configuration properties are provided in the “Configuration Page Overview” chapter of the PureWeb Server Administration Guide.

Found In:  4.0.0

The following message may be displayed when you install the PureWeb iOS STK on Mac OS X 10.8 (Mountain Lion) (Issue# PWEB-2821):

"PureWebSetup.pkg" can't be opened because it is from an unidentified developer.

Workaround:

  1. Navigate to System Preferences | Security & Privacy | Allow applications downloaded from:
  2. Select the Anywhere option.
Found In:  3.1.1

The PureWeb 4.0 server cannot restore configuration backup files from versions of PureWeb that are older than PureWeb 3.1. If upgrading PureWeb to 4.0 from a version earlier than 3.1, please ensure that you have copied and safely stored any configuration files that you still need. (Issue# PWEB-2208)

Found In:  3.1.0

The PureWeb installation directory path cannot contain any spaces. Changing the default installation directory to C:\CSI\Pure Web will result in a File Not Found Exception. (Issue# PWEB-737)

Found In: 3.0.0

When using Windows Server 2008, you must modify the User Access Control (UAC) settings, so that the user can edit and save configuration files. If the user has the wrong permissions, and they attempt to save a modified configuration file, an Internal Server Error will be displayed. (Issue# PWEB-919)

Found In: 3.0.0

The PureWeb uninstaller does not remove shortcuts from the Windows' Start menu. This can cause confusion with new shortcuts created during PureWeb installation. After uninstalling PureWeb 4.0, the Calgary Scientific folder should be manually deleted from the ../Windows/Start Menu/Programs directory before installing the new version of PureWeb. (Issue# PWEB-2479)

Found In:  3.0.0

Top of Page


Discontinued and Deprecated Support

This section documents features that are no longer supported in this software as of release 4.0, as well as features that are deprecated and will be discontinued in an upcoming release. 


Dicontinued Items

The following API is no longer available in PureWeb 4.0:
If you were using this API in your applications to set preferred remote image format, refer to the PureWeb 4.0 Upgrade Notes for information on how to achieve the same results using the new and improved image encoding functionality.

Deprecated Items

The PureWeb clustering capability to support multi-server environments is being deprecated. Instead, we recommend using a load balancer to support such environments.

The following PureWeb client STKs are being deprecated:
Support remains for these client STKs in PureWeb 4.0, but we may remove support for them in future versions.

For anyone who is new to PureWeb, we recommend that you develop clients using the HTML5, Flex, iOS and/or Android client STKs.

For anyone who is currently using the Java Swing and/or Silverlight client STK, we recommend that you consider migrating to one of the other client STKs.

Top of Page


Additional Information

Additional information on Calgary Scientific Inc. is available on our website

Top of Page