All I can suggest, if they won't make an exception, is to find a
different provider that is a better fit for you. I've been at the
other end of this problem at HMS, where I've had sites that won't stay
up because someone else is taking out the server with long running
templates or some other code issue and I've had to move to a different
HMS shared server.

Even if your need is legit, you must be able to see what their problem
is: let's say (for example) there's 10 threads available to CF and
someone's downloads take 5 minutes each. That means that we only need
10 people to do those downloads at the same time and the server will
be completely unresponsive to anyone else for 5 minutes. Perhaps a VPS
or dedicated solution is necessary in this case (or rewrite the code
so it doesn't tie up a thread for the whole download).

On 12/30/06, Mary Jo Sminkey <[EMAIL PROTECTED]> wrote:
> >We also apply max timeouts with fusionreactor that causes similar problems,
> >but if a client has a page that needs to run longer, we ad dit to the
> >exclusion list.
> >Perhaps u can ask HMS to do the same.
>
> I'm trying! But as others in the thread have mentioned, this seems to be 
> their policy on shared servers, no exceptions or exclusions.
>
> Oh, just thought of another instance where my customers will be effected by 
> this...those that use verity searching on their stores, the indexing often 
> will take a couple minutes to run if they have a lot of pages and products. 
> So this will kill that process as well.
>
>
> --- Mary Jo
>
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Create robust enterprise, web RIAs.
Upgrade & integrate Adobe Coldfusion MX7 with Flex 2
http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:265374
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to