Thanks for your response Bill.
With regards to your qn, yes, some user interaction might be required. Something more than just a HTML page with search results is needed. For eg. when the user gives the initial search request, it could be --> display available car model (all year, all prices). Once the results are displayed in a grid form, they might want to use a sliding bar that is on top of the grid to narrow the year range OR price range. The idea of the applet comes from the applet found in cars.com (search used cars) which is neat and interactive. (see link below)
http://www.cars.com/carsapp/national /?srv=adlocator&act=index&zc=06053&flt=zr%2Cn_ms%2Cused&tf=/quick_usedforsale-index.tmpl&ct=used&rd=10 The search would be done on a database that has all data pertaining to cars/models/price.
Client side-
(1)A simple form to get the user's search criteria
(2)The search results displayed in a grid with sliding bars on top for narrowing the selection further
Server side
(1) Database search procedure
(2) Populating the grid with the search results and sending it back to the client
(3) Handling user interaction to refine the grid data
Am I approaching the problem right with regards to identifying the client/server tasks?
This being a specific requirement, I am not sure if I should bring it up in a general discussion forum like this. Javaranch moderators, please let me know if I should email any specific individual in this regard.
Thanks
Viji
[This message has been edited by Viji Bharat (edited January 15, 2001).]