The servlet has access to all information inside the container/context that may be needed to do the job. For an external job this can be much harder. (Iterate over all sessions to do something with them, access attributes with application scope, access attributes from server.xml/ web.xml) It's also easier to protect resources from concurrent access (to synchronize them if nessesary).
The actions are triggered locally, the access to the servlet is restricted to local hosts. > -----Original Message----- > From: Nikola Milutinovic [mailto:[EMAIL PROTECTED] > Sent: Monday, January 05, 2004 12:19 PM > To: Tomcat Users List > Subject: Re: Threaded servlets okay in a compliant container? > > > Why is it easier to do those things from a Servlet, than a > regular shell script? > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
