I have a requirement to cater for a large number of results returned to the presentation tier. I've taken a quick look into the Value List Handler Design pattern (http://java.sun.com/blueprints/corej2eepatterns/Patterns/ValueListHandler.html).
I do agree it offers some advantages but in my opinion it doesn't satisfy its goal. From the sample code it appears that the SQL Resultset is completely loaded and represented as a list of Transfer Objects. When dealing with a large result this will have a negative impact on performance as it must create a TO for each record.
I could make some changes to increase performance i.e.
Store the ResulSet as a member of the ValueListHandler Object and only load the data from the resultset as and when i need it. If i store the ValueListHandler in HttpSession i got to ensure i close all connections before disposing of it, other wise i could max out on cursors.
Anyone got any ideas/suggestion as to how best to implement such functionality?
_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
