| ... |
... |
@@ -16,4 +16,4 @@ |
| 16 |
16 |
|
| 17 |
17 |
First of all, by using a frontend server, you can separate your internal intranet from the external internet. You might configure your network in such a way that the master server is accessible only within your intranet. This increases security, as a master server manages sensible form and personal data. Form the outside network, end users only need to be able to access forms. And this is the (only) service a frontend server provides. |
| 18 |
18 |
|
| 19 |
|
-Secondly, you can setup more than one frontend server. These frontend server can cache forms, which provides a light form of load balancing. However, please note that the single master server still needs to [[process>>doc:Formcycle.UserInterface.MyForms.WorkflowProcessing.WebHome]] all the form data by itself. If you need better load balancing, consider setting up a [[cluster>>doc:.UserInterface.Cluster.CommonConfiguration]] with several master servers. |
|
19 |
+Secondly, you can setup more than one frontend server. These frontend server can cache forms, which provides a light form of load balancing. However, please note that the single master server still needs to [[process>>doc:Formcycle.Designer.Workflow.WebHome]] all the form data by itself. If you need better load balancing, consider setting up a [[cluster>>doc:.UserInterface.Cluster.CommonConfiguration]] with several master servers. |
