The other sticking point is that no one wants you to have long running processes, e.g. WebKit.
That is true. It's not even worth trying to set up WebKit on a shared host unless they specifically support it.
I don't think the situation is as bad as that. I have Webware running on a cheap shared Linux box. Of course you cannot install mod_webkit, but WebKit.cgi works and you can always find a spare port to run on. The most difficult part of the installation was stripping WebWare down to fit in 10MB with the rest of my things. (It would be nice to have a doc-free and perhaps sample-free installation option.)
Maybe you can get by with that for a while (I don't want to jinx you or anything ;), but it's probably because your host isn't maintaining the system very well. At some point someone is likely to abuse the ability to run long-running processes (like start an ircd server or something), or the hosting company is going to change its policies or software infrastructure, and you're going to find you app is periodically killed.
I think there exist ways to robustly manage a server with Webware users (because you still have to deal with runaway processes and the like), but I don't think any of the commodity sites are going to do that. You might find one that is not robustly managing their servers, but that doesn't seem like a good compromise ;)
Ian
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
