TSO Host

I am using Ajax controls
...
From memory, my code itself doesn't have any urls listed.

Holy contradiction Batman! :P

AJAX means you're communicating with the server. Communicating with the server means you're sending data to a script on the server. The way you send data to a script on a server is via a Uniform Resource Locater.

Either way, you can see for yourself - fire up firebug, or any other browser-resident debugging tool that'll show you what HTTP requests get made, and see them - it's trying to hit files that aren't there. I don't know why they aren't there, maybe you didn't upload them, but that's why there's problems with those buttons.
 
I thought I would post some comments about hybrid/linux/windows hosting.

The customer service rep told me that the hybrid server and windows server should handle aspx pages in an identical way. The only difference is that a hybrid server cannot handle aspx pages without an extension.
With Linux bias, the 'default' pages (default.xxx, index.xxx etc) are handled by the Linux servers and with Windows bias, they're handled by Windows (which is where the 'bias' part comes in). Ultra-flexible essentially.

In any case, I think the best way for anybody who is running asp pages, would be to set up a (Windows server) sub-domain and then run the asp pages separately in that subdomain. This way, you are guaranteed to have 100% compatibility without any issues of missing .asp or .aspx extensions.
I think that's the best option here as it's simpler than debugging your app most likely :)
 
I think that's the best option here as it's simpler than debugging your app most likely :)

Yep.

Also, as I make further changes to the web application, in the coming months, by hosting on a Windows server, any code that works on the development machine is almost guaranteed to work on the TSOHost's server.

It just saves a lot of hassle by having a separate sub domain handling asp/aspx pages.
 
Last edited:
Hi,

Thanks for letting me know that suarve.

The issue is now sorted, so load times have decreased to acceptable levels (and not the 14s-20s load times I was initially seeing).

In a nutshell, if you want to run a php site, with TSOHost at least, it is best to use a Linux server.

If you want to host an asp/x page, its best to use a Windows server.

Hosting the php part of the site on a Windows server resulting in load times of between 14s-20s.

When you run a Hybrid server, with Linux bias, the server is essentially a linux server. Everything gets sent to it, as per normal. However, if any file/url extensions have .asp or .aspx on the end, these will get handled by a separate windows server.

Both the Linux and Windows server will have access to all the data on your web page.

Now, I'm pretty sure that it is more complex than what I have explained above, but I believe those are the main points.

Now, to configure a subdomain and assign it with an Windows server is such a no-brainer, IMO that should be the default method of hosting a website which uses both php and asp/x. Not running a hybrid server.

The above technique, cuts out ALL the headache that may occur if you are attempting to use the hybrid server, ie. your asp/x page not working, once it is uploaded to the webhost (although it worked fine on your development machine).

Based on my own experiences, I would advise against using a hybrid server - use it only if you absolutely have to.

Having been through the above though, I believe TSOHost offer fantastic value for money, where webhosts which offer both Linux and Windows hosting, at an affordable price, with good bandwidth allocation and good reliability, are very rare.
 
Hi,

Thanks for letting me know that suarve.

The issue is now sorted, so load times have decreased to acceptable levels (and not the 14s-20s load times I was initially seeing).

In a nutshell, if you want to run a php site, with TSOHost at least, it is best to use a Linux server.

If you want to host an asp/x page, its best to use a Windows server.

Hosting the php part of the site on a Windows server resulting in load times of between 14s-20s.

When you run a Hybrid server, with Linux bias, the server is essentially a linux server. Everything gets sent to it, as per normal. However, if any file/url extensions have .asp or .aspx on the end, these will get handled by a separate windows server.

Both the Linux and Windows server will have access to all the data on your web page.

Now, I'm pretty sure that it is more complex than what I have explained above, but I believe those are the main points.

Now, to configure a subdomain and assign it with an Windows server is such a no-brainer, IMO that should be the default method of hosting a website which uses both php and asp/x. Not running a hybrid server.

The above technique, cuts out ALL the headache that may occur if you are attempting to use the hybrid server, ie. your asp/x page not working, once it is uploaded to the webhost (although it worked fine on your development machine).

Based on my own experiences, I would advise against using a hybrid server - use it only if you absolutely have to.

Having been through the above though, I believe TSOHost offer fantastic value for money, where webhosts which offer both Linux and Windows hosting, at an affordable price, with good bandwidth allocation and good reliability, are very rare.

Yer, when I first signed up with them a few years ago, one of the main benefits for me was the ability to host both asp and php sites from the same control panel. The PHP sites flew, but at the time (and this has probably changed since I last used the feature) the asp sites had a noticeable extra second loading time - however, they were nasty, basic classic ASP sites anyway :) I set the server type to hyride with linux bias if that made any difference.

If you're interested, it may be worth asking ecactly how it wotks on their forum - as Darren/Adam are highly likely to answer, as the forum is pretty active. :)
 
Back
Top Bottom