My point exactly. What's the cost/benefit? The hosting would have to cost $75 USD per month or more...at that point, you might as well give them a virtual private server.
Shared hosting could work, but I think at that point you have to start picking your market. For example, Canada Webhosting (http://www.canadawebhosting.com) offers a UNIX reseller plan that hosts 10 domains and has PHP and Tomcat 4. The cost is $38.95 USD/month, that's $3.90 USD/month/domain. That's an incredibly low price, and it doesn't matter where their customers live. In their scenario, if you want ASP, that's a different account on a different machine, with a different pricing structure. Don't forget about licensing...you need a couple thousand dollars to legally offer IIS hosting, just in software licenses alone. At shared hosting price levels, and by the time you figure in soft costs for support of a complex architecture like having ASP and Tomcat on the same or different machines, it will take years to see a return on your investment. Just my opinion, obviously, but if I was going to be a webhoster, I would just do it virtually and resell someone else's packages. I wouldn't start from scratch and build everything. Starting from scratch is attractive from a geek pride perspective, but it's suicide from a business perspective, unless you're willing to charge big money for a 100% custom solution and you can find the customers to buy it. John > -----Original Message----- > From: Jose Antonio Martinez [mailto:lfbbes@;yahoo.es] > Sent: Tuesday, November 12, 2002 8:18 AM > To: Tomcat Users List > Subject: RE: windows iis machine + linux tomcat machine > > > imagine i want to offer jboss too... then i would have > to have: windows+iis+tomcat+jboss , and > linux+apache+tomcat+jboss ... and few people using it. > > > --- "Turner, John" <[EMAIL PROTECTED]> escribi�: > > > Keep it simple. You keep trying to worry about > > syncing drives up. I think > > that's more complex than things need to be. > > > > In your .properties file on the IIS machine, just > > use the FQDN of the Tomcat > > server and be done with it. > > > > IIS is horrendously slow using mapped drives to > > serve content. > > > > I'm not criticizing, just observing. You can't be > > everything to everyone, > > if you are starting a business you will go bust > > quickly trying to be > > everything to everyone. Pick your market...in my > > experience, if someone is > > developing with ASP, they will have no desire and no > > incentive to develop > > with Tomcat. Seems to me it would make a lot more > > sense to have an > > IIS+Tomcat server and an Apache+Tomcat server, and > > assign customer accounts > > accordingly, instead of creating a very complex > > architecture. > > -- To unsubscribe, e-mail: <mailto:tomcat-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-user-help@;jakarta.apache.org>
