>Java VM, then on DataDirect for the JDBC drivers, and then on JIntegra for
>COM support (if you need it), and only finally on Macromedia for the CFMX
>application server. All of these are good companies with good technology,
>but there are several layers of complexity here, none of which is supported
>or endorsed by Microsoft.
I don't mean to burst your little BlueDragon pitch, but what about the
problems that arise when you put all your eggs in one basket? I'd
rather rely on different companies for different parts of the
application, rather than just assume MS can do it better than anyone
else, which is rarely the case. I think the freedom to switch core
technologies like JVM and JDBCs as a positive thing.
What sort of benefits are thier in giving up the freedom to move platmforms?
-Adam
----- Original Message -----
From: Vince Bonfanti <[EMAIL PROTECTED]>
Date: Tue, 28 Sep 2004 11:23:15 -0400
Subject: RE: ms to no longer supporting msjvm
To: CF-Talk <[EMAIL PROTECTED]>
No, it doesn't, since both CFMX and the Java editions of BlueDragon run on
Java VMs provided by Sun. It does raise an interesting point, however: Java
is basically a "foreign" technology layered on top Windows and developed by
a third-party (Sun) who hasn't always been on the friendliest of terms with
Microsoft.
Put another way, both CFMX and the Java versions of BlueDragon rely on Sun's
Java VM as their technology platform. Java is not supported or endorsed by
Microsoft in any way--in fact, Microsoft has been actively antagonistic to
Java and Sun. Worse, the use of Java as a technology platform for CFMX
requires reliance on other third parties for crucial pieces of
technology--such as the DataDirect JDBC drivers and the JIntegra software
for COM support.
Think about it: when deploying CFMX, you're relying first on Sun for the
Java VM, then on DataDirect for the JDBC drivers, and then on JIntegra for
COM support (if you need it), and only finally on Macromedia for the CFMX
application server. All of these are good companies with good technology,
but there are several layers of complexity here, none of which is supported
or endorsed by Microsoft.
Contrast this with BlueDragon.NET, which relies on the Microsoft .NET
Framework as it's underlying technology. The .NET Framework, of course, is
developed by Microsoft and is tightly integrated with Windows. Database
access (ADO.NET) and COM support are built-in natively to the .NET
Framework, so no need for additional third party software. So instead of the
Java-DataDirect-JIntegra-CFMX stack (none developed, endorsed or supported
by Microsoft!), you've got a much simpler .NET-BlueDragon stack on top of
which to run your CFML applications.
The best part is that BlueDragon.NET is certified and endorsed by Microsoft,
so you've got an entire stack that is either developed, supported, or
certified by the platform vendor:
http://www.microsoft.com/resources/casestudies/CaseStudy.asp?CaseStudyID=158
64
The point of all of this is: if you're running on Windows, using .NET makes
a lot more sense than using Java, which means that using BlueDragon.NET
makes a lot more sense than using CFMX (or the Java editions of BlueDragon).
The only reason to use Java on Windows is if you want your applications to
be portable to Linux, UNIX, or Mac OS X. If you only intend to deploy on
Windows, then you should use .NET instead of Java.
Vince Bonfanti
New Atlanta Communications, LLC
http://www.newatlanta.com
________________________________
From: Tony Weeg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 28, 2004 9:25 AM
To: CF-Talk
Subject: ms to no longer supporting msjvm
http://www.microsoft.com/mscorp/java/
this has ABSOLUTELY no adverse affect on us right?
--
tony
Tony Weeg
macromedia certified cold fusion developer
email: tonyweeg [at] gmail [dot] com
blog: http://www.revolutionwebdesign.com/blog/
cool tool: http://www.antiwrap.com________________________________
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
