you wrote:
> > 2. As I mentioned before, you also assume WO will be used only
> > for Internet use, where the cost of communications lines are high.
> > Our apps are for intranet use where bandwidth is practically free.
>
> Could you explain how the cost of communications (as opposed
> to the number of concurrent users) have an effect on the
> cost of deployment for WO?
The relevance, as I understood it, is this: you can only use as
many TPM as would saturate your link to the internet.
In other words: a load-balancing, multi-CPU web server does no
good for an internet app, if you're connected to the internet
with a 28.8 modem over SLIP.
Then the issue comes up: if your application requires a T3
connection to even provide the bandwidth, you're probably
also in a league where you can afford the $25k for WO, given
that you have to pay several k$/month just for the net
connection...
Of course, as others have pointed out, that doesn't account for
intranet apps, which could be as simple as a web based message
board for a department, something one could whip up with WO and
OpenBaseLite in about half a day. It is these many trivially
simple apps that WO is not getting, even though it could do
the job wonderfully, simply because the cost can't be justified.
Often it's these trivial apps that evolve over time, are merged
etc. Thus capturing market and mind share is key.
Ronald
==============================================================================
"The reasonable man adapts himself to the world; the unreasonable one persists
in trying to adapt the world to himself. Therefore all progress depends on the
unreasonable man." G.B. Shaw | [EMAIL PROTECTED] | NeXT-mail welcome
