Re: Database Maintenance Models -- JAVA400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

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

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.