Regular Expressions

Appendix C: Compatibility With Previous Versions of the UNIX Option

This chapter discusses the compatibility between the UNIX Option provided on NetExpress Version 3, and that provided on NetExpress Version 2. In the following sections the phrase "old UNIX Option" refers to the UNIX Option provided on NetExpress V2.0; the phrase "new UNIX Option" refers to the UNIX Option provided on NetExpress V3.0

C.1 Saved Settings

The UNIX Option settings are stored in the NetExpress project file. The format in which these settings are stored has been updated for NetExpress V3.0. Except in the case of file mapings, the old UNIX Option settings are automatically converted to the format for the new UNIX Option, and default values assigned, whenever changes are made to the UNIX Option settings.

The old UNIX Option had no concept of filetypes and transferred everything as binary. Therefore, when an old filemap is loaded all files are assigned a binary type rather than the normal new UNIX Option default of text.

C.2 Restrictions

The old UNIX Option did not separate the saved data into server-specific and project specific-sections. This has the following impacts.

• Last Publish time

  The last publish time defined by the old UNIX Option is ignored by the new UNIX Option.

• CGI support

  CGI support was defined on a server-by-server basis in the old UNIX Option. It is defined on a project basis in the new UNIX Option. The first server loaded from the old UNIX Option server enables or disables the CGI support flag.

• Enable File Mapping

  In the old UNIX Option:

  • Filename mapping could be enabled or disabled. If filename mapping was disabled then the native PC filesystem names were used
    .
    
  • Although the filename mapping information itself was project wide, the enablement of filename mapping was server specific.

  The new UNIX Option does not allow filename mapping to be disabled. All filename mapping information is project wide. The server used as the default in the old UNIX Option is used to determine whether filename mapping is enabled or disabled when the project file is first loaded. If filename mapping is enabled, the existing filename mapping information is used. If it is disabled, the filename map is populated with file system information.

C.3 Client/Server Compatibility

The client/server protocol used by the old UNIX Option has been updated for the new UNIX Option. This includes both functionality enhancements and significant performance improvements. The protocol stream includes version checking which enables newer components on one platform to inter-operate with older components on another.

If you have a NetExpress V2.0 client publishing to a server that has a new NetExpress V3.0 SCP program installed, there are no compatibility problems.

If you have a NetExpress V3.0 client publishing to a server that has an old NetExpress V2.0 SCP program installed, you should be aware of the following limitations:

• While it is possible to define logical directories in a project, the real directories associated with the logical directories must be the same as the real directories for either [BuildDir] or [CopyDir]; that is, there can be a maximum of two real target directories
  
  
• There is no support for source verification operations
  
  
• There is no support for automatically creating directories on server
  
  
• The output pane in the NetExpress IDE does not show the progress of the server build. The output pane is only updated when the build is completed on the server
  
  
• You cannot stop a publish once the build on the server is active
  
  
• There are no Publisher performance improvements
  
  

Regular Expressions