A java applet using EOs makes the tpm pricing model look foolish. With
client side EOs you will have transactions occurring when you do stuff like
fetch and save. This means that a very simple applet in the hands of a
single user can "stall" the server. I have found that even in the
development stage the 25 tpm model is completely inadequate as I can stall
the server running simple tests. I can't see how any reasonable java
application using EOs can be deployed without an unlimited license.
The WO pricing model may have some logic when it comes to serving vanilla
web pages on the internet, but it makes no sense for Java app development.
Its sad to see such a great tool crippled by a pathetic pricing model.
-----Original Message-----
From: Georg Tuparev [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, March 09, 1999 1:45 PM
To: Multiple recipients of list
Subject: Re: Unfair WO4 pricing
Folks,
Could anybody comment on the tpm issue when using the new Java client? I
still had no serious project with Java client, but my first impression was
that the line is getting hot ;-) How is this translated in terms of tpm's?
later
-- georg --
---
Georg Tuparev <[EMAIL PROTECTED]>
The ObjectZoo Ltd.
Schipbeekstraat 1 3 Cathles Road
1078 BK Amsterdam, The Netherlands London SW12 9LE, UK
Mobile: +31-655-798196 Fax: +31-20-524-1254
Windows NT is NOT a virus - a virus is small and efficient!
