1. Title to and ownership of the software and documentation shall remain with the Contractor.
2. Use of the software and documentation shall be limited to the facility for which it is acquired.
3. The Government shall not provide or otherwise make available the software or documentation, or any portion thereof, in any form, to any third party without the prior written approval of the Contractor. Third parties do not include prime contractors, subcontractors and agents of the Government who have the Government's permission to use the licensed software and documentation at the facility, and who have agreed to use the licensed software and documentation only in accordance with these restrictions. This provision does not limit the right of the Government to use software, documentation, or information therein, which the Government has or may obtain without restrictions.
4. The Government shall have the right to use the computer software and documentation with the computer for which it is acquired at any other facility to which that computer may be transferred; to use the computer software and documentation with a backup computer when the primary computer is inoperative; to copy computer programs for safekeeping (archives) or backup purposes; and to modify the software and documentation or combine it with other software. Provided that the unmodified portions shall remain subject to these restrictions.

The most current list can be obtained from the InterSystems Website.

Users should check this list periodically to obtain the latest information on issues that may have an effect on the operation of their site.

• Phone:  +1  617  621-0700
• Fax:  +1  617  734-9391
• Email:  support@intersystems.com

1. A request from browser A is assigned to Cache process X and marks the session as state-aware (sets Preserve=1).
2. Browser A then issues a new request which terminates the state-aware session (by calling EndSession()). This action sets Preserve=0 and ends the session on the server. However, browser A still has a session cookie marked as state-aware.
3. Browser B issues a request which is assigned to Cache process X (since this has been returned to the pool of state-less connections) and marks the session as state-aware.
4. Finally, browser A (which was left open) issues a request which is erroneously routed to Cache process X (which is now exclusively owned by browser B). Cache responds to this security violation by halting process X.

Under these conditions, the Gateway then records the following error in its event log:

However, this is context-sensitive and in this class '%ClassName' is just the argument to the macro as well so it is not valid to expand this inside an INC file.

Caché now detects this and avoids expanding this until an application invokes this macro.

If the application was changed so that a subclass overrode method, X, the class compiler was not detecting this and calling the wrong method. It now properly invokes the overriding method.

This has now been corrected.

If the configuration file was edited by hand, this could cause problems at startup when Caché attempted to mount the database.

This has been changed so that Caché only checks the collation when it is entered via the Management Portal. Furthermore, it only checks the collation of the physical global when the mapping entered is a subscript-level mapping.

If two independent events cause conflicting DOM updates, then the user may be presented with an inconsistent user interface. The $JOB value on the server does not guarantee that threads will not be processed out of order and can lead to false thread assertion problems depending on how requests are processed.

This change uses a unique value generated on the client browser to identify logical threads instead of using the $JOB value from the server.