|
Choosing Between Local and Server Templates |
|
|
Choosing Between Local and Server Templates |
|
Starting with XF Rendering Server version 5.0.0 software developers can choose to combine XML and XSL or XFD templates on both the client or the server side.
The following table summarizes the differences between the two:
Local (Client) Templates |
Server Templates |
- Are files that reside on the same computer as the user's .NET or Java application
|
- Are files that reside on the same computer as XF Rendering Server; in many cases, XF Rendering Server runs on the same machine as the user's application. |
- Require no special configuration |
- Must be configured in the Management Console as server templates |
- Good if the user desires to distribute processing between the client and the server |
- Good if the user desires to concentrate all processing on the server |
Transformation Engine |
.NET Client |
Java Client |
C++ Client |
Server (Windows) |
Server (Linux) |
MSXML |
x |
x |
x |
||
DOTNET |
x |
x |
x |
||
Saxon |
|
x |
x |
x |
x |
Java |
x |
x |
x |
x |
Notes:
| · | The user can have a Linux/Unix client (Java, PHP) call a remote instance of XF Rendering Server running on Windows. |
| · | The opposite is also true: Windows client (.NET, Java, PHP) applications can call a remote instance of the server running on Linux. |
| · | In both cases, to make remote calls from another computer to a server that is running XF Rendering Server the user must simply initialize Server and ServerPort from RequestParamters to the required values. The default value for ServerPort is 1099. The default value for Server is localhost, that is, the local computer. |
| · | Server Templates are also available on Linux and AIX operating systems for the Java and SAXON engines. |