Thanks for the offer. My point was to point put Cold Fusion has a large footprint
and there are many technical hurdles to overcome to have a Cold Fusion application
on a CD (forgeting about licencing issues with SQL Server and CF).
P.S. What is your current schedule for the .net version.
As a consulting company, a working .net version provides of compelling solution
for our clients-- a code base with very few changes working across all platforms.
Jeremy Brodie
Edgewater Technology
web: http://www.edgewater.com
phone:(703) 815-2500
email: [EMAIL PROTECTED]
>Hi Jeremy,
>
>FYI, BlueDragon very nicely addresses both the technical and licensing
>issues you raise. Again, if you're interested I can have someone from our
>sales and/or technical staff contact you with details.
>
>Vince Bonfanti
>New Atlanta Communications, LLC
>http://www.newatlanta.com
>
>-----Original Message-----
>From: Jeremy Brodie [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, February 17, 2004 12:15 PM
>To: CF-Talk
>Subject: Re:cf web app on a cd?
>
>
>Forgetting about the licencing and pricing issues (see strong recomendation
>at the bottom of post) for a moment (for CF and SQL Server), you probally
>will not be able to run CF from a CD for the following reasons:
>
>Even using apache/Tomcat CF takes up at nearly 300MB of space (nearly 1/2 of
>the CD). This does not include any compoents (Java runtime engine, services
>interfaces or any other component that might be installed outside the Tomcat
>application.)
>
>This would not include any programs that would autoluanch apache/Tomcat or
>any database functionality. Nor would it include your application or any
>space to run your application. This would also not add the permissions
>necessary to run Tomcat properly as well -- since Tomcat or any other J2EE
>server requires local administration permissions to reach certain resources.
>
>Adding a Database (forget about SQL Server) would at least another 50-90
>MBs, assuming you're using mySQL as your database. SQL Server is really tied
>to the operating system so it will be hard if not impossible to run.
>
>Before ASP.net entered the fray, it was much easier to move applications
>into ASP using Microsoft's Personal Web Service-- having support for ASP out
>of the box. With ASP.net other overhead exists making CD versions not as
>attractive.
>
>When you add licencing issues (Microsoft makes you pay for each connection
>unit, CF on a dual CPU basis.) then very quickly you'll see the reason why I
>would (strongly) not recommend anyone going down this path.
>
>Better to ask if the client has some Internet conductivity and would be
>willing to go down the Flash client/CF, SQL Server server route instead.
>This way you are not placing your client at a legal risk.
>
>Jeremy Brodie
>Edgewater Technology
>
>web: http://www.edgewater.com
>phone:(703) 815-2500
>email: [EMAIL PROTECTED]
>
> _____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
