Dan Melomedman writes:
> IMHO piped I/O and CGI
> is not scalable, neither is multi-process model of Sqwebmail and Apache,
> but this model provides for a lot of flexibility.
sqwebmail has supported fastcgi for a very long time. Is this too slow for
your purposes?
There are lots of webservers out there besides Apache. Try flask or xitami
if you like the event-driven model.
> The size on my system for an older version is around 300K stripped.
The size on disk doesn't matter nearly as much as its size at runtime. How
much memory does sqwebmail take up under load on your machine?
> fork() is very expensive
Have you measured it? Under linux, for instance, forking and creating a
thread are essentially the same thing.
> and the larger the executable the more IMHO expensive it is.
Since forking is copy-on-write I'm not sure I follow your logic here. Can
you explain?
> What I'd love to see in the future is something like Sqwebmail, but with a
> web server built-in and multi-threaded using an easy, scalable threading
> library like http://oss.sgi.com/projects/state-threads or pthrlib from
> annexia.org.
From what I can tell the state-threads project aren't really threads. It
looks like an event-driven library.
It seems like most of your concerns have more to do with the web server than
sqwebmail.
Justus
