On Mon, Jan 4, 2010 at 3:47 PM, jtd jtd@mtnl.net.in wrote:
On Monday 04 January 2010 14:29:32 sankarshan wrote:
On Mon, Jan 4, 2010 at 2:22 PM, Saswata Banerjee & Associates
scrapo@saswatabanerjee.com wrote:
There is an exe file that my client downloaded (after ubantu failed to install apache from its own repository for some reason) When the exe was run, it first installed apache server on windows then it installed mysql on windows and then copied the php codes to the relevant folder and created the database in mysql initiated the browser and took it to the login page of the crm.
What you are pointing out is a function of packaging the application and, configuring the dependencies/requirements appropriately so as to enable install the application plus the relevant packages and, then using a sample configuration file to start the service.
You are presuming
- All the expertise of making your app run on doze is available with
the developer 2) That the performance and support issues will remain the same as with linux 3) That doze environments are homogenous
Not at all. I was just pointing out that the requirements that the install-configure-work_with_it experience on Linux can be easy and, there are somewhat simple steps to adhere to. An ISV which is looking at quick adoption would be aware of the need to compress the time from the application is procured/purchased to when the application is productized.
There was no assumption of Microsoft products/platforms at all.