Queries providers from within R3Hotel aplication without necessity of calling remote Polaris service over remoting.
Polaris engine dll (Polaris2.dll) is referenced directly in R3Hotel project. There is no need to serialize requests/responses and transmit them over remoting anymore.
Feature is available from version 3.3 of R3Hotel application, and Polaris 10.3.
Since there is no need for serialization and no network traffic between R3Hotel and Polaris, there is a noticable improvement of total response time. Depending of server utiliztion it was up to 7 seconds in basic tests on acceptance environment.
IIS proces for R3Hotel application may have too high memory utilization volume (using Memcached to hold cache data is highly advised!)
- web application is less stable, since all communication and processing is done within it
web.config of R3Hotel application must contain all sections from Polaris config
- same applies for platform.config and applications defined there
local reference to Polaris will be used only, when R3Hotel's web.config contains following setting:
appSettings/Polaris2-IsLocalReference = "true". Otherwise remote Polaris service will be queried.
<appSettings> <add key="Polaris2-Url" value="tcp://oft_acc:4321/Polaris2Engine"/> (used when below setting is false or missing) <add key="Polaris2-IsLocalReference" value="true"/>
<add key="Polaris2-Url" value="tcp://oft_acc:4321/Polaris2Engine"/> (used when below setting is false or missing)
<add key="Polaris2-IsLocalReference" value="true"/>