Dated: July 20, 2004
We now have a new Cold Fusion MX 6.1 Enterprise server - WinCF. This server is a dedicated Cold Fusion server with no ASP.NET, ASP or Frontpage support. PHP and Perl are however supported
We have 2 versions of our Windows plans now - Standard and CF. All new customers from this date onwards will have to choose between the Standard and CF versions of the Value, Silver, Gold, Plantinum and Titanium windows plans. This does not apply to exisiting customers and they will continue to enjoy all features they signed up for on their server. New Windows plans are available at http://www.jodohost.com/windows.asp
This decision has important implications for resellers. Resellers will not be able to sell Cold Fusion MX with ASP.NET/ASP/Frontpage support anymore. The economics of installing Cold Fusion MX on each server (like we were doing so in the past) does not make sense. Cold Fusion costs us $6000 per server with less than 5% of the sites actually using them. Putting Cold Fusion MX on a separate server is an industry standard and only we at JodoHost have chosen to put it on every server.
It is strongly recommended that resellers create new Cold Fusion MX plans. When creating a new Windows plan, resellers can now choose what server group the plan should use. Choosing the "win servers" group means all accounts on this plan would go to a standard windows server (no cf support) while selecting the "Cold Fusion servers" group would mean all accounts would go to a CF server with CF, PHP and perl support (in this case, WinCF)
All new signups will now be going to Win5 which is a non-cold fusion server unless a plan is configured to the Cold Fusion servers group. Accounts created on plans configured to the Cold Fusion server group would go to the new WinCF server. This change in policy will NOT effect resellers immediately. Although signups will be going to Win5, resellers can request Cold Fusion accounts that need ASP/ASP.NET/FP support to be shifted to Win6 which is a full Windows server with Cold Fusion MX. This option will be available to resellers for a period of upto 2 weeks but can be extended upto 4 weeks for a reseller if so required. But we do however urge our resellers to reconsider their marketing strategy over the next few weeks and create new Cold Fusion plans at the soonest so they are not dependent on us.
We understand some resellers will be disappointed with our decision but we'd like to once again stress that what we are now switching to is an industry wide policy where hosting companies have separate servers with Cold Fusion alone. We have however chosen also to enable PHP and Perl. This will in time improve performance for both Cold Fusion and non-cold fusion customers as well as reduce the potential for server problems or crashes
Before resellers begin creating CF plans, please add WinCF as a server alias from E.Manager > Server Aliases. If you require any help in plan creation, please email [email protected]. What we have done for our shared plans is simply created a copy of each of our individual plans, renamed them, changed the server group and have disabled ASP, ASP.NET and frontpage (took us under 30 minutes). To copy a plan, press the "Copy" icon next to it and to change it's name, click "Settings"
We now have a new Cold Fusion MX 6.1 Enterprise server - WinCF. This server is a dedicated Cold Fusion server with no ASP.NET, ASP or Frontpage support. PHP and Perl are however supported
We have 2 versions of our Windows plans now - Standard and CF. All new customers from this date onwards will have to choose between the Standard and CF versions of the Value, Silver, Gold, Plantinum and Titanium windows plans. This does not apply to exisiting customers and they will continue to enjoy all features they signed up for on their server. New Windows plans are available at http://www.jodohost.com/windows.asp
This decision has important implications for resellers. Resellers will not be able to sell Cold Fusion MX with ASP.NET/ASP/Frontpage support anymore. The economics of installing Cold Fusion MX on each server (like we were doing so in the past) does not make sense. Cold Fusion costs us $6000 per server with less than 5% of the sites actually using them. Putting Cold Fusion MX on a separate server is an industry standard and only we at JodoHost have chosen to put it on every server.
It is strongly recommended that resellers create new Cold Fusion MX plans. When creating a new Windows plan, resellers can now choose what server group the plan should use. Choosing the "win servers" group means all accounts on this plan would go to a standard windows server (no cf support) while selecting the "Cold Fusion servers" group would mean all accounts would go to a CF server with CF, PHP and perl support (in this case, WinCF)
All new signups will now be going to Win5 which is a non-cold fusion server unless a plan is configured to the Cold Fusion servers group. Accounts created on plans configured to the Cold Fusion server group would go to the new WinCF server. This change in policy will NOT effect resellers immediately. Although signups will be going to Win5, resellers can request Cold Fusion accounts that need ASP/ASP.NET/FP support to be shifted to Win6 which is a full Windows server with Cold Fusion MX. This option will be available to resellers for a period of upto 2 weeks but can be extended upto 4 weeks for a reseller if so required. But we do however urge our resellers to reconsider their marketing strategy over the next few weeks and create new Cold Fusion plans at the soonest so they are not dependent on us.
We understand some resellers will be disappointed with our decision but we'd like to once again stress that what we are now switching to is an industry wide policy where hosting companies have separate servers with Cold Fusion alone. We have however chosen also to enable PHP and Perl. This will in time improve performance for both Cold Fusion and non-cold fusion customers as well as reduce the potential for server problems or crashes
Before resellers begin creating CF plans, please add WinCF as a server alias from E.Manager > Server Aliases. If you require any help in plan creation, please email [email protected]. What we have done for our shared plans is simply created a copy of each of our individual plans, renamed them, changed the server group and have disabled ASP, ASP.NET and frontpage (took us under 30 minutes). To copy a plan, press the "Copy" icon next to it and to change it's name, click "Settings"