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
