> at a time. SkunkWeb uses a forking process model, which
> makes resource sharing more complicated in certain
> circumstances, it will fully utilize all available
> processors," ... "so SkunkWeb scales better."
In two and a half years of working on icecast, we've been doign threads
almost the whole time, because it works better. Forking versions
weren't as efficient, and data access is much easier IMO with shared
data among threads (with proper safeguards of course) than with all
the forking mechanisms for doing the same.
Also, threading is quite portable, even to Windows, while forking is
only really portable on Unix-like systems.
jack.
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/webware-devel
