Links

Lists

Latest Updates

Ruby On Rails List
Python list
Advanced Java
The JavaScript List
Apache Users
Full Disclosure
Linux Security

Search the archives!


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Design Issue


  • From: anand_cp/Polaris@xxxxxxxxxxxxx (anand_cp/Polaris@xxxxxxxxxxxxx)
  • Subject: Design Issue
  • Date: Fri, 31 Dec 1999 13:11:10 +0530


Dear Rahul,
Developing an intranet applet-based database application necessiates taking into
account several issues:
They are described here in order of importance:
1. Deploying the application: Developing is only 25% of the story. The remaining
75% is deployment. Plan well on how you plan to deploy it. i.e., whether you
want to deploy it on a web-server or a just a shared machine, does the
web-server contain the database server also, or whether the database server is
separate, etc., how big will be the application (swing or no swing AWT) etc. You
must also take into account which browser your clients will be using (IE 4.x or
Netscape 4.x or mixed), because your development should be tuned to client's
browser. There are also issues involved in both browsers, like no support for
RMI in IE, non-uniform user-interface display between IE and netscape (swing
standardizes it), both browsers have different security restrictions, speed at
which client can connect to server (this decides the size of your applet).
2. Accessing DB server: It makes sense if the clients use a mediator to access
the database instead of connecting to it directly. For example, If you have 1000
clients, you don't to hit the database 1000 times to fetch a resultset. First of
all, you may not   have 1000 licenses, and secondly your DB server will be down
to its knees imm'ly.
Try to use an intermediate application at the server end which will connect to
database on request from a client, execute the query, close the connecttion and
inform the client what transpired. This is useful in managing connections to
database since you will be opening and closing connections very fast. Add a
queuing effect to pool connections and you will be re-using 10/15 connections
with very fast turnaround time.

Hope this gives you some idea of what to do.
Regs.
C.P. Anand

Environment jdk1.2.2 Winnt
Hi All,
I am develping an Intranet application in which my Applets want to
communicate with the DataBase.
Can anybody please recommend me the best way to do it. I dont want to use
servlets. .
Should i use sockets or RMI.
should i connect directly with the Database using thin driver.
Any suggetions will be helpful
thanks in Advance
Rahul



---
To unsubscribe, mail advanced-java-unsubscribe@xxxxxxxxxxxxxxxx
To get help, mail advanced-java-help@xxxxxxxxxxxxxxxx