Do absolute url prefixes for links on a godaddy hosted website eat up more concurrent connections?
Posted on 2007-10-05
We have a client who's starting to experience some really heavy traffic on his GoDaddy-hosted website.
Now that the traffic has spiked significantly, it's not uncommon to sometimes see the following when trying to access the website:
Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance
downtime or capacity problems. Please try again later.
One of the GoDaddy "customer support" guys expressed a "theory" of his that ... if we have absolute url prefixes in our code (which we do) -- then it treats each link as another connection -- and each call effectively eats in to the amount of concurrent / simultaneous users that can access the site (something about the sessions for each user getting lost when using absolute url prefixes, etc).
Personally, .. I think it's bullsh*t. For example, .. there are many PHP apps and shopping carts, etc. that intentionally incorporate absolute url prefixes for all of their links. It's very common practice.
So what's the deal, really? Do absolute url prefixes for links on a godaddy hosted websites really eat up more concurrent connections? Has anyone else come up against this? I ask because we're now gearing up to apply all kinds of revisions to the website in attempt to remove all these absolute url prefixes, and as a courtesy to our client, .. I think we should spare him the expense if it's needless.
So do you folks smell bullsh*t too? Or is this Godaddy customer service dude on to something, perhaps?