If you're committed to ASP, we don't know of a faster one.. sorry. On the other hand, designing high speed, high volume applications works well in Java. You can create multiple threads executing concurrently, each accessing data quickly using JDBC dynamic prepared statements or static SQL. Obviously you need to clearly identify WHERE the performance problem is. If 90% of the delay is on the iSeries in database access (vs. transfer using ODBC), then you need to simplify the data access better with indexes, logical views, perhaps a read-only data mart concept.
Also, Java has the advantage of being able to process data on the iSeries or a PC. If processing on the iSeries, you could send the "net" results, not all the data, to the PC, improving performance. Many options exist for this : applet to servlet, application to servlet, etc. RMI can do this also but is probably not your fastest option.
================================== MORE INFORMATION ON THIS TOPIC ==================================
Ask your Web development questions--or help out your peers by answering them--in our live discussion forums.
The Best Web Links: tips, tutorials and more.
Check out this live Q&A with Dave Slater and Jim Mason, How to best get started with WebSphere Development Tools.
Search400's targeted search engine: Get relevant information on machine interface (MI).
This was first published in July 2002