On Saturday, Nov 9, 2002, at 16:42 US/Pacific, Dick Applebaum wrote:
> So, there are no implied benefits to the purchaser, that because he is
> charged per CPU, CFMXJ2ee will perform better on on (or take better
> advantage of ) multiple CPUs than CFMX Enterprise Server.
Full J2EE application servers generally provide sophisticated
clustering and fail over options, as well as a number of other
features. As may be evident already from some of the threads we've seen
here, setting up a full-blown J2EE application server so it is properly
tuned and configured is a much bigger deal than setting up CF
standalone - CF was designed to be (relatively) easy to set up.
> Many will likely ask: "Why shouldn't I just buy a CFMXJ2ee license for
> a single CPU, regardless of how many CPU's the box has?".
Actually, many won't. As I said in my other email, enterprise software
customers are used to paying per-CPU - see below for information from
Microsoft about per-CPU licensing.
> It appears that this sort of pricing is artificial, and nudges
> customers to be dishonest -- since I can't see how it can be enforced.
Well, it *can* be enforced because most systems let you interrogate how
many CPUs they have.
> Why not just charge based on product capabilities?
More CPUs means more capacity so in a sense you *are* paying based on
capability.
> Do Server OS platforms charge based on the number of CPU'? -- At least
> they would have a valid reason and an enforcement mechanism.
Some do, yes.
Here's a quote from Microsoft's Server Product licensing document:
"The current license policy for Microsoft� server products offers
customers a choice between three modes: (i) Per Seat mode (ii) Per
Server mode and (iii) Per Processor mode. Customers may select the
mode that best suits their organization�s needs. It is possible to
have different types of servers licensed in different modes. It is not
necessary to notify Microsoft of the licensing mode selected.
Regardless of which mode the customer chooses, a server license is
required for the right to run any given copy of the server software on
a particular system. Some options may require the acquisition of a
Client Access License (CAL) for each client�s right to access a
particular server product. Microsoft�s current policy, however, leaves
it up to the customer to choose the Server licensing mode that best
fits their needs where choices are available.
With Per Seat licensing, a CAL is associated with a specific computer,
device or �seat�. Using this alternative, client computers are allowed
access to any server on the network running the particular server
application for which that client machine is licensed.
With Per Server licensing, a CAL is associated with a particular
server. This alternative allows concurrent-use licensing; i.e., if a
customer decides to use the server in Per Server mode, he/she must then
have at least as many CALs dedicated to that server as the maximum
number of clients that will connect to that server at any one point in
time.
With Per Processor licensing, no CALs are needed; the right to access
the server is covered by the server license itself. So any one, any
time, any where, from any device that has the proper permission from
the server owner may access the information on that Per Processor
licensed server."
More information can be found here:
http://www.microsoft.com/servers/howtobuy/default.asp
> Sorry to be so stupid, but I am not familiar with the server side of
> the business.
No problem. Licensing is a vast black box and there are many options.
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription:
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
