Good news...

[dvanburen]

Originally Posted by Ballyhoo

I love good news...
Just wondering as the goodness is flowing if there might be a...
6. Ruby on Rails

Don't plan on seeing ruby anytime soon. From what I have seen it is way too resource hungry to run on our shared servers. Of course we could do this with a dedicated server.

[Ballyhoo]

Originally Posted by admin

1. More Techs. --done
2. 24/7 level 1 and sales live chat. --done
3. ASP.NET 2.0 coming soon. --next maybe
4. PHP 5 coming soon. --after #3? this one is needed for Drupal upgrade
5. Hiring a full time sales person.. --doesn't effect us as far as I can see

6. Ruby

Originally Posted by dvanburan

too resource hungry to run on our shared servers.

First time I have come across that. If that is the case on "our" servers then by all means lets find a-work-around, wait for that to be addressed by future roll-outs or drop the idea.

[dvanburen]

Originally Posted by Ballyhoo

6. Ruby
First time I have come across that. If that is the case on "our" servers then by all means lets find a-work-around, wait for that to be address by future roll-outs or drop the idea.

It's not even on my agenda. If you want Ruby, go dedicated.

[dpyers]

The PHP 5 upgrade should have plenty of lead time. Breaks a lot of 4.x scripts... and 5.1 breaks some 5.0 things... and 5.2 breaks some 5.1 things... Really seems like 5 was put together by a committee - lol.

Did some work with RoR and was not impressed. Good for simple AJAX CRUD interfaces but anything more complicated requires writing it's own controller/handler for the model. PHP CRUD interfaces aren't a particular problem for me but extending a RoR app even a little bit gets very complicated very fast.
RoR AJAX doesn't degrade well at all if a visitor has javascript turned off - which isn't a big deal for me, but is for some.

I also believe that there's a fundamental security flaw in the way RoR model features are exposed in the url.

[dvanburen]

Originally Posted by dpyers

The PHP 5 upgrade should have plenty of lead time. Breaks a lot of 4.x scripts... and 5.1 breaks some 5.0 things... and 5.2 breaks some 5.1 things... Really seems like 5 was put together by a committee - lol.

The reason we are waiting for 2.5.1 (Maybe 3.0) is that it incorporates a way for the end user to choose which implementation of PHP they want to run. This should all but eliminate any broken scripts when upgrading. It has this functionality for ASP.NET as well.

[Ballyhoo]

Would that be per domain or per plan?

[dpyers]

Originally Posted by dvanburen

The reason we are waiting for 2.5.1 (Maybe 3.0) is that it incorporates a way for the end user to choose which implementation of PHP they want to run. This should all but eliminate any broken scripts when upgrading. It has this functionality for ASP.NET as well.

That's really good news. Will the same version selection capability be available for MySQL and MS SQL?

[Brangwyn]

The PHP 5 upgrade should have plenty of lead time. Breaks a lot of 4.x scripts...

I don't know how HSphere handles it, but personally I have 4 and 5 running side by side on my servers and the users can simply choose which version they want to run on a per domain basis.

[dvanburen]

Originally Posted by dpyers

That's really good news. Will the same version selection capability be available for MySQL and MS SQL?

No, we will only be running one version of each. 2005 MSSQL servers may be added in the future, but there are no current plans to implement them.