major disappointment on hsphere 3 windows side :(

Well I had some decent hopes for a few settings on hsphere 3.0 for giving resellers real control over their application needs, there was a setting for application directory, but it is useless and does nothing but give the directory EXECUTE permissions for apps, which is not really useful because we have the servers locked down with web service extensions, and do not and WILL NOT allow rogue EXE fiels to execute. It doesn’t make a windows application folder, or virtual directory as I’d hoped.

next thing is in the reseller plan wizard it has an option to allow “dedicated application pools”
I don’t know what what going through their head when they made this but it doesn’t make a dedicated pool at all, if you change this setting it simply makes your existing pool(which may have others in it) to have a web garden! a web garden is NOT a good thing unless your app is distinctly designed for it, a web garden can literally wreak havoc on your sessions, page loads, viewstates, and cause some major programming headaches.

We will be disabling this “dedicated application pool” as it is causing mass confusion and major headaches because it is NOT what it says it is, once they make it correct, we will enable it. At this time it is simply not what it claims to be.

A web garden rather than a dedicated pool? That just doesn’t make any sense at all.
I’d say there’s some room in the market for multi-platform hosting solutions. Unfortunately I don’t have the time or resources to set up such a large undertaking. It might have been interesting :slight_smile:

yes it is horrible in fact, a dedicated all pool would resolve session issues that may occur and seems to be one of biggest needs for such a pool, while a web garden simply makes the problems whatever magnitude the number is set to worse! so 2x=2x worse session problem, there setting the reseller to allow “5 dedicated app pools” would make it 5x worse!

the whole situation makes no sense at all, its been reported on psoft forums to not use it in any case, and we just ran into the first errors with a client using it as well.