Difference between revisions of "1.0.2 Release Notes"

From GCube System
Jump to: navigation, search
 
Line 3: Line 3:
 
====Changes Related to the gHN====
 
====Changes Related to the gHN====
  
:* ''new configuration parameters'': the gHN can be optionally configured to declare to run in a host name and port different from the real ones. Two new gHN configuration parameters, namely ''publishedHost'' and ''publishedPort'', are now available for this purpose. This new possibility is offered to those that want to install a proxy or a dispatcher (clearly running on the published host and port) that acts as an intermediary for requests from clients and the real gHN. For further information, see the related [[Administrator_Guide#Configuring_the_Container|configuration]] section in the gCore Administration Guide.
+
:* ''new configuration parameters'': the gHN can be optionally configured to declare to run in a host name and port different from the actual ones. Two new gHN configuration parameters, namely ''publishedHost'' and ''publishedPort'', are now available for this purpose. This possibility is offered to Site Managers that want to install a proxy or a dispatcher (clearly running on the published host and port) that acts as an intermediary for requests from clients and the real gHN. For further information, see the related [[Administrator_Guide#Configuring_the_Container|configuration]] section in the gCore Administration Guide.

Latest revision as of 23:21, 28 June 2010

gCore 1.0.2 introduces the following changes:

Changes Related to the gHN

  • new configuration parameters: the gHN can be optionally configured to declare to run in a host name and port different from the actual ones. Two new gHN configuration parameters, namely publishedHost and publishedPort, are now available for this purpose. This possibility is offered to Site Managers that want to install a proxy or a dispatcher (clearly running on the published host and port) that acts as an intermediary for requests from clients and the real gHN. For further information, see the related configuration section in the gCore Administration Guide.