Originally posted by Avi Abrami:
Lots of missing information here that affects the answer. A ResultSet is like a database cursor. One of the details you don't mention is the DBMS you are using. With my experience (with both Oracle and Informix), a database cursor is something available via the DBMS's procedural language extension - in Oracle this is PL/SQL and in Informix it is SPL. Both these DBMS's (Oracle and Informix) know how to handle huge result sets via cursors, so a java.sql.ResultSet should also be handled just as well. Therefore, if the cursors don't cause performance problems, why should the ResultSet? There are obviously some other details you haven't mentioned.
We use RMI to return ResultSets to a remote client by building java.util.Collections. The ResultSet remains open on the server and the client can navigate the ResultSet remotely and receives Collections that can be of varying sizes from one row (of the ResultSet) to the entire ResultSet (memory permitting). We use large ResultSets and don't notice any performance problems. If, however, you open several ResultSets simultaneously, then you start to see problems.
More details about your situation would help. What is your architecture - client/server, remote clients, local clients? What is your DBMS - Oracle, Informix, SQL Server, Cloudscape? Do you have a java application or applet (or servlet or JSP or what)?
Cheers,
Avi.
Originally posted by kuaikuai:
//User clicks SWITCH IDENTITY, we are require to abandon
// existing session & switch to new login user
// Code snipplets below
HttpSession session = request.getSession();
if (session != null)
session.invalidate(); // destroy everything on session
// We then require a Total new session
session = request.getSession(true);
In Jrun3, The session above returns the old session which
will throw exception if we call
session.putValue ("Name", "XX");
Anyone can suggest how I can access a new session
Originally posted by Pranav Jaidka:
hi thilak
JSP was made in order to give the user a distinct method to separate the HTML (interface part) from the actual servlet methods(Actual functionality).So it depends on what you need to use.
If you wantyour servlet to use HTML extensively you can go in for JSP as it saves you a lot of trouble.
If on the other hand your servlet is just a pure functional unit then you may prefer to go in for the Servlet approach.
The jsp format allows you to use certain objects like out,request and response so theres not much difference in what you can do with servlets and jsp .
regards
pranav