> From: Vamshidhar Palkonda [mailto:[EMAIL PROTECTED]
> Today, all the embedded devices like VPN, Firewall devices
> have a cli, httpd and configd daemons. These are all control
> pane daemons. They are all in C/C++.
>
> Now I want to use tomcat in place of httpd and confid. First
> is it a good way to go in that direction.
How much space do you have on the embedded device? You'll need a Java
SE runtime (*not* ME) in order to start Tomcat. If you don't already
have Java on the device for other purposes, this is a significant
overhead. What OS are you running on the embedded device, and is there
a J2SE port for it?
> I have to figure out a way to hook cli to communicate to
> tomcat.
Why? What are you communicating? Can you (for example) make a JNI
library to retrieve the same information through API calls?
> The reason why I want to use tomcat is the ease of
> development. I can use JSF for the EMS.
That *has* to be the first time I've heard "JSF" and "ease of
development" in the same paragraph :-).
> or do u guys think I am better of some httpd, and configd
> implemented in C.
I think you're best off with the technology that your development team
knows, unless you're starting from scratch. Do your developers already
know Java and JSF? If not, what do they know?
- Peter
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
