Web Server Application?
Added by Matthew Kettlewell over 14 years ago
I'm looking at using WT, and got a bit confused on the terminology of where the Web Server Application is...
Is it just the FCGI app?
In a traditional CGI in C, I would just have each user start a new process... but it appears that's not the case here?
If someone could be so kind as to explain how the Web Server Application ties in to each process/user that would be grand... or if there's a document that I've missed, that would be even better ;)
Thanks
Matt Kettlewell
Replies (1)
RE: Web Server Application? - Added by Wim Dumon over 14 years ago
Hi Matt,
Wt is a library to build web applications, which can be connected to the web through one of the connectors:
- FCGI connector: an external web server is used as frontend to Wt. Not available on Windows.
- ISAPI connector: Microsoft IIS is used as web server frontend to Wt.
- wthttp conenctor: when using this connector, your Wt application is a standalone application which includes a webserver.
With respect to processes: with the ISAPI and wthttp connector, all sessions run within a single process. With the FCGI connector, this is configurable in wt_config.xml: either every session runs in its own process, or a process is shared with a few sessions, or all sessions run in one process.
The advantage of using wthttp is that the built-in webserver has all the right features implemented in the right way for Wt (e.g. we recently implemented websockets support for better responsiveness). It's fully asynchronous and can therefore handle high server loads without a problem. Often, a web server configured as reverse proxy in front of a wthttp application is an ideal deployment method.
BR,
Wim.