> 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.
Your browser might open 4 HTTP connections but that doesn't translate
into 4 WOApp hits. Not unless you have something like images on your
page that in turn are filled by the WOApp instead of the HTTP server
itself. If that is the case, then you probably want to use new features
of WOImage instead of whatever WO
action invocation you are using now to return images from your WOApp,
because like Eric said, WO doesn't count (as transactions) images vended
out via WOImage's data binding even if they ARE directly vended by the
app (as, say, a server-side GIF generated using the WO Plot.framework).
The only other way one page load would cause more than one WOApp hit
would be if you have a bunch of applets or JavaScript on the page that
start talking back to the WOApp after the page loads into the browser.
If you don't have images/client-side-activity then what you are saying
makes no sense to me and I certainly don't observe it with my customers.
I suspect your app has a frameset with at least three frames. You are
probably referring to reloading the top level frame which in turn causes
the three content frames to load. In this scenario you would have 4 page
loads. One for the frameset page, 3 more for the content pages filling
the frameset. But then, you would only have these hits on the _top frame
reload. Not when you weren't loading framesets. if you ARE reloading
framesets like that at _top on each request then that smells of pretty
gnarly design... i.e. why use frames at all if you always reload all of
them on each request. Frames are useful mainly when you use them to
avoid reloading real-estate.
d
Afshin Behnia wrote:
>
> 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.
>
> -----Original Message-----
> From: Eric Noyau [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, March 08, 1999 5:35 PM
> To: Afshin Behnia
> Cc: Multiple recipients of list
> Subject: Re: Unfair WO4 pricing
>
> At 17:22 3/8/99 , Afshin Behnia wrote:
> >[...]
> >
> >The problem with this new licensing is that at the $7499 level, 100 tpm is
> >useless! Our application hits over 25 tpm with ONE user using the app
> >normally, so 100 tpm should be only good enough for 4 concurrent users
> max,
> >versus the 50 users under the old licensing.
> > [...]
>
> First of all, I'm not participating in any discussion pertaining to
> licensing and pricing so I cannot really help you there. Talk to your Apple
> representative.
>
> But I'm curious how you can get to 25 tpm with one user. A WebObjects
> transaction is one round trip from the user web browser to your
> application, not counting the images (usually directly served by your HTTP
> server anyway).
>
> So basically you are saying that your users are downloading and viewing 25
> pages per minute? Can you explain what your application does? I'm just
> curious. With a highly interactive application like the WOInfoCenter it's
> pretty damn near impossible to hit the 25 tpm restriction unless you are
> not reading anything and just clicking like mad on the links.
>
> -- Eric
