Hi Punam,
In your kind of scenario applet/html-servlet looks suitable. Instead of
writing a text let me come to your specific points, to the best of my
knowledge.

>*       We thought of applets for the frontend and servlets on server side.
>Applets because as all marketing ppl like, there are gonna be
graphs,reports
>and comparisons of all types. I thought html would not give us graph
>facility. Is applets and servlets a good combination?

You can use a mixture of HTML and Applet as client with servlets. For graphs
etc you have to go for applet. For simple feedback form I think HTML is good
enough. But if you have some dynamic choice loading kind of stuff (like
populate the states with the selection of country) you might think
otherwise.

>*       For the applet to communicate to the servlet, we decided on using
>the url connection method. The other method i know of is to use rmi. Which
>is better and why?

url connection is the easiest one. RMI can be used, but it has some
limitations as well. You can get the details in the following article.
http://developer.java.sun.com/developer/technicalArticles/RMI/rmi/

>*       Should there be multiple servlets for various business logics or
>everything should be in one servlet itself?

You can have multiple servlets. Everything in one servlet is a bit mess. You
can think about delegation also instead of writing multiple servlets. Refer
the following article for delegation model. To me it looked like a very good
maintainable solution.
http://www.javaworld.com/javaworld/jw-09-1999/jw-09-servlet.html


>*       I really donot know what architecture do such applications
typically
>have. I would know where to get documentation on such
>architectures.(internet/book)

I don't know what you meant by architecture here.

Typically you will have a database manager to interact with database. In
your scenario I guess simple database transactions are needed. So you can
write your own. In complex scenario you might think about Application
Servers to manage your database transactions. I don't think you will need
that.

Servlet will get the requests from HTML/Applet client in HTTP and get it
serviced with this database manager and give back the response to the
client.

For showing some graph and all some data transfer protocol has to be decided
between servlet and applet.

See if it helps.
Soumya Sankar Basu

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to