Re: Database Maintenance Models

[Marc Logemann <spam1@xxxxxxxxxxxx>]

Nathan Andelin wrote:

> > Servlets are multi-threaded.  That's the whole idea.
>
>
> More precisely, Servlet containers are multi-threaded, placing the burden on
> Servlet and framework developers to synchronize their methods.  If one (1)
> Servlet is responsible for database inquiry and maintenance for so many
> files, supporting so many users, wouldn't that be a serious bottleneck for
> high-volume sites?

The Front Controller Servlet normally dispatches the tasks to different 
plain java classes and they do the work. But thats more an architectural 
 issue, you could also do all the stuff in this threaded Servlet, why 
should this be a bottleneck? It makes no difference if the CPU shares 
its time to 10 threads within one servlet or with 10 different servlets. 
Doesnt make much of a difference.

And yes, you are correct, the container fires the thread, so technically 
speaking the servlet itself does not know much about threads, meaning it 
doesnt implement Runnable or something. But generally people (including 
myself) use the term "Servlets are multithreaded", just for the sake of 
simplicity.

BTW, i liked your HTML screenshots, very well designed web UI.

Marc