Some of that i agree with, like it should be better suited for shared access. But then again I have a crap load of sites running on my vps and there is no problems.
I hate to say this to you but the only problems I seem to have are with your cart timing out constantly, I get those all the time 5, 10, 15, 20 times a day and thats kind of the same thing isnt it? But im not complaining about your code and setup, I just take it how it is. They do try and track down those on shared servers that are causing problems, I have been asked countless times if I can fix the code on the cart that times out (when it was on shared server) and I have been asked to remove large cfdocument tasks and I know a few people there really well and I generally get the inside scope and its happening all the time. as far as it giving cfm a bad name, well then.. I visit plenty of php and .net sites all day long that are constantly down and its no surprise that they all are on shared servers. People on here always have said that if you have problems with your hosting when you are doing it cheaply then go with your own server and I used to balk at that but now I understand what they mean. It "should" and probably "could" run better than it does but it doesnt help you right now and if you go somewhere else you will end up with same problems. Its kinda like with the cart errors, I can live with them but it gets old and I have seen that its a common problem that you are addressing in the future but it doesnt help me now. And i am not knocking your cart cause its a great cart but its parallel to your argument here. Personally, I was getting frustrated as well with the sites being down and I did something about it, while it was more $$, after putting a dozen or so client sites on it, it pays for itself and I pocket the rest, plus I get to host all my sites for free, no reason not to do it. > > you gotta remember cfm wasnt made to work as a shared server. > > Maybe not originally, but again, that's no excuse for it still not > working properly as a shared server. It will have a hard time being > successful long term if it is not. > > > > and i wouldnt blame hms, blame some bad code from someone on the > > server (aka will). > > Again...that's just an easy excuse. First, it shouldn't be so easy for > someone to bring down the whole server. Second, if someone is > routinely doing so, then HMS should track them down. Most people > running sites don't *want* to bring the server down...but they are > often not able to make that determination themselves that their site > is the problem. > > > > bottom line is that if you are on a shared server you are at the > mercy > > of other peoples code that can bring the server down, HMS has gotten > > > pretty strict about bad code on the shared servers but still... If > you > > want better uptime then get your own vps at least. > > Look, I can accept that on a shared server, my site may once in awhile > go down. I understand that. But when it's a daily thing...that's a > problem, and one that should be addressed. It gives ColdFusion a bad > name if it becomes typical to visit a CF site and get a jrun error > instead. > > > --- Mary Jo > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJQ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:274914 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
