From: Nicolas R. <nic...@gm...> - 2014-12-04 07:54:51
|
Hi Volker, I agree with Alexis and François-Xavier. A few additional comments on esigate-server : > > 2) esigate-server is a pre-packaged version of the EsiGate filter deployed inside a Jetty server. It is easy to run and you have nothing to install, that is why it is often used in development. I think you could safely use it in production but it still lacks some features like init scripts (but this is currently in progress) so you would have a little work to setup everything In the 4.X branch you cannot configure provider mappings in esigate-server. Threads, max connections, … are also not configurable. This is why it is not suited for real projects. In the 5.x branch, these issues are fixed. It can be used the same way than esigate-war, but this setup is less tested than the standard one. The whole 5.X branch is still in development. It is quite stable, but configuration/behavior may slightly change before release. Using it during development ensure there are no upcoming breaking changes for your project. If you find any bug, feel free to open issues on github. -- Nicolas |