> > That architecture was explored in detail by Netscape. It isn't reliable
> > and slows your web server to a crawl whenever dynamic content is produced.
> > It should only be used for static file servers and caching gateways, and
> > people implementing those might as well use an in-kernel server like TUX.
>
> i'm confused... what architecture has that problem with dynamic content?
>
> i can believe it if you're referring to a userland threading library,
> single process server.
>
> i can't believe it if the threads are scheduled by the kernel (either as
> 1:1 or 1:many).
>
> NSPR threading was probably to blame, no?
Does NSPR do userland threading on Solaris? I thought they were using native
threads. But you are right, the dynamic content problem was for libraries
that are not thread-safe and for platforms that had userland threads. They
ended up with some funky stuff in NSAPI that made the generic API slower
than mollasses (internal modules used another API).
....Roy
