Kbase 17897: What changed from Apptivity 2.0 to 2.1?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
What changed from Apptivity 2.0 to 2.1?
This kbase addresses some questions users may have with regard to the
with regard to the move from Apptivity 2.0 to Apptivity 2.1.
It is recommended that users read the Apptivity 2.1 release notes
to learn about the most important release information as a first
step after installing the new release. For the latest release
note information see the Apptivity web site
(http://apptivity.progress.com). A link to the latest copy of
the release notes may be found in the release notes which ship
with the product.
What changes have been implemented in version 2.1?
The 2.1 release is a maintenance release. The goal of the
release was to address issues affecting the deployment of
Apptivity applications. Apptivity 2.1 includes improved
quality, performance, and stability. HTTP Tunneling is a
new feature added for web deployment situations. Finally,
the OpenLink PROGRESS ODBC driver is included for development
time access to the PROGRESS database.
Are there any changes which would impact code developed
with Apptivity 2.0?
There are no changes which should impact code that was
developed with Apptivity 2.0.
Are there any changes in how the IDE generates code?
There are no changes to how code is generated or run.
Projects written in Apptivity 2.0 can be opened and run in
Apptivity 2.1 without any modification.
Will the server perform differently?
The server design for Apptivity 2.1 is the same as for
Apptivity 2.0. An HTTP tunneling feature was added for
Apptivity 2.1 to help with deployment of applets behind
firewalls, however this feature must be explicitly
turned on in the new release. HTTP tunneling should only
be used if an applet cannot be deployed using the standard
socket configuration. For more information about this
feature, see the Apptivity 2.1 release notes.
What if my code runs differently in Apptivity 2.1 than
in Apptivity 2.0?
It is recommended that users test their applications on
Apptivity 2.1 before deploying the applications for
production.
If an application which was developed with Apptivity 2.0
behaves differently in Apptivity 2.1 users are encouraged
to contact their Apptivity Support representative to have
the issue researched. Please see the Apptivity web site
for details about how evaluators and commercial customers
can contact Support.
5/6/98
UTF
Apptivity 2.0/2.1
Progress Software Technical Support Note # 17897