Unless you are serving images via the database, the simultaneous
connections don't matter (I don't know if image hits against the slave
worker threads count-- if they do, don't serve images via the Web App...
there is a lot of reason to not do so anyway (scalability and flexibility
of the serving environment, mainly).
Alternatively, if you have lots of frames, each frame and each frameset
will represent a transaction. (Frames are generally really evil anyway--
they are very hard to get right, cause all kinds of problems, suck down
server resources, and can be highly confusing to both the user and the
devleoper).
The transactions/minute rating applies *only* to the Web Apps-- not to the
web server...
b.bum
