Hmm, according to my error logs, the most requested components at my site are /winnt/system32/cmd.exe and /htdocs/scripts/root.exe. Couldn't resist. ;-) Good point about which components to consider, though-- may be able to make many folks happy with minimal disturbance. Some sites run an "experimental, at your own risk" server with some extras, for their most vocal customers. Putting the double handful of whingers there can often be simpler than losing their business, though admittedly it doesn't scale for very large providers. SRC Rachel Luxemburg wrote:
Track which components are being asked for and consider supporting for the more popular ones. We did this when I was at Virtualscape and found it to be an easy way to differentiate your service and make customers happy.
At 02:04 PM 10/19/2001 -0700, Christopher J. Wolff wrote:
Also, what are the groups opinions on web hosting customers who want to install custom ASP and COM components on a shared Windows 2000/IIS hosting server? I'm having a debate with a sales dude over this issue.
My opinion is that it potentially destabilizes all of the virtual hosts on that system. When I hear "Can you install just a couple of ASP or COM components on my domain" my mind immediately goes to putting this customer in their own dedicated colo server. I don't think its right to jeopardize several hundred virtual domains because one $19.99/month customer wants to load up a special .dll. But that's just my rant, market conditions can dictate otherwise.
-- ======================================================================== Strata Rose Chalup [KF6NBZ] strata "@" virtual.net VirtualNet Consulting http://www.virtual.net/ ** Project Management & Architecture for ISP/ASP Systems Integration ** =========================================================================