At Wed, 2 Jun 2010 00:10:39 -0600, OvermindDL1 wrote:
Few words about Wt model:
- It holds server side live object for every user session which is quite huge overhead for high traffic web site.
There is a quote from their docs:
> Thus, for every new session, Wt spawns a new process. > This has the main benefit of enjoying kernel-level memory protection > between user sessions.
I don't think that it is true for latest versions but it is quite bad design for scalability.
I certainly know that is not true when hosting on Windows, on *nix I believe it uses FastCGI. The user session data is only important for when the user *has* a session (logged in or so?), otherwise you are free to kill the session once served. The amount of data it holds is only your own design, can be as little or large as necessary.
Wow, this Wt thing looks really, really cool. I don't suppose they want to be part of Boost? -- Dave Abrahams BoostPro Computing http://www.boostpro.com