Randy
> I'm curious... Does WebObjects count the retrieval of an image as a
> transaction?
Not unless you really work at it! By default if you bind a WOImage's
data= binding to server side state (instead of a filename=), WO will
create a page with a special URL that will cause the browser to get the
image for its src= from the WOApp instead of the HTTP server. However,
this WILL NOT COUNT toward the tpm you get. Consider that in
DirectConnect mode ALL the images you see are fed out by the WOApp and
you might have hundreds of these per page! (So it's nice that WO spews
image data back in mutliple threads so even while your page is loading
(possibly huge) image, another user can hit the app and ask for another
page and get it back immediately.)
Now, if you created your own DirecAction, say, that returned image data
and bound that directly to the src= binding on a WOImage, then, yes,
that would count as a transaction. Note this may sound silly but if you
had a WO3.5.1 app that did something like this to workaround WO3.5.1's
WOImage's lack of a good facility for the same, your ported WO3.5.1 app
might still be using this wasteful scheme even after porting to WO4. To
fix that you would only have to REMOVE code, and in its place wire data
directly to WOImage's data binding. See the Create Plots demo example
for more on feeding WOImage data directly from a WOApp.
d
Randy Wigginton wrote:
>
> One user using one browser generates *ONE* page request; the number of
> images on the page may make up another n transactions (where n could be any
> number), but these go against the web server, not the webobjects adapter.
>
> I'm curious... Does WebObjects count the retrieval of an image as a
> transaction? If so, this would be a good incentive to use images that are
> served up by the web server and not processed by webobjects.
>
> I have personally not run into the 25 TPM limit, except when trying to.
>
> >One user using one browser typically creates multiple simultaneous HTTP
> >transactions to the server. Netscape Navigator, for example, is by default
> >set to make 4 simultaneous transactions each time the user interacts with
> >the server. As such, if a user makes 5 request to the server per minute
> >(which is a very reasonable and conservative amount) that translates to 20
> >tpm from WebObject's point of view. This means that 5 simulataneous users
> >will generate 100 transactions per minute. This has been confirmed by our
> >developers. They are constantly hitting the 25 tpm limit of the developer
> >version even with just one user.
> >
>
> -- randy
