Re: Servlet init(). & configuration changes.
- From: "John C. Bollinger" <jobollin@xxxxxxxxxxx>
- Date: Tue, 21 Jun 2005 21:41:26 -0500
Yogee wrote:
> John C. Bollinger wrote:
[...]
> I m using the Java tech. for first time in my life. So, the review is > obvious. Thanx for enlightening me. Also where can I read internals of > servlets.
You can download the servlet spec from Sun for free: http://java.sun.com/products/servlet/download.html#specs
The latest version is 2.4, though there are still plenty of servlet containers out there that implement only version 2.3 (e.g. Tomcat 4.x), and some that are at earlier versions.
You may also want to look into JSP for the UI part; that spec is a separate download, but it ties tightly into servlets.
>>> Second question: >>> ------------------- >>> >>> There are other stand alone components which need to be notified of any >>> configuration changes. Is it a good idea to use telnet for this >>> components from the web interfaces to inform about changes in the >>> configuration. >>> >>> All the components are bound to work in a LAN with all ports open >>> across each other. >> >> >> The most appropriate mechanism for notifying other components surely >> depends on the details of those components. Telnet from the web >> interface doesn't sound particularly attractive, though. Better by far >> would be for your central configuration resource to actively notify the >> necessary components. >> > > All the configurations are stored in a database, when a person changes > the configuration, its the interface which knows about the changes > happening. So, I thought why not tell from there itself. I know its not > a GOOD thing. > > Lets consider this: > > Changes happened in database. Interface knows it, but cant tell? > Database can't tell anyone, unless someone do a select.
That's the least common denominator, to be sure.
> Other senario can be I run a provisioning server, central repsoitory > for configurations. It will keep all conf and everyone needs to have > permission from it to run the stuff. I can expose some applet on the > web that then talks to the PServer. It can be then used to do all sorts > of things.
Something along those lines is what I had in mind. An important aspect to this, in response to your question about notification, is that your provisioning server can have a mechanism to notify registered listeners about configuration changes.
> OR, > > SOAP. (Its last thing..)
SOAP is a different kettle of fish. It could conceivably be the *means* of notification, but it's just a protocol and cannot serve as the *agent* of notification. In any case, if you already have standalone applications that you want to notify then the details of those apps determine the available means of notification. Unless they're already tooled for it, SOAP probably isn't a particularly viable means.
-- John Bollinger jobollin@xxxxxxxxxxx .
- References:
- Servlet init(). & configuration changes.
- From: Yogee
- Re: Servlet init(). & configuration changes.
- From: John C. Bollinger
- Re: Servlet init(). & configuration changes.
- From: Yogee
- Servlet init(). & configuration changes.
- Prev by Date: Re: hashCode for 4 ints?
- Next by Date: Re: hashCode for 4 ints?
- Previous by thread: Re: Servlet init(). & configuration changes.
- Next by thread: Newbie-help! API 0 Results = errorpage.jsp, i need the 0 returned
- Index(es):
Relevant Pages
|
