Reply to thread

Message

<blockquote data-quote="Arnix" data-source="post: 323154" data-attributes="member: 5521">You would also use a sub domain to seperate certain sections of your site, or to do distributed hosting (part of site on one web server, another part on another web server).If you had player info you could have players.mydomain.com instead of mydomain.com/players (a waste) or you could host player info off of a free site and have player.mydomain.com pointing to it, but maintaining you main site on the mydomain.com's host.&nbsp; This could help for bandwidth or speed issues.&nbsp; Split heavy traffic sections up on multiple cheap site with low bandwidth restriction and it will appear as one site, but using different bandwidths.You could also have a sub domain pointing to the cgi-bin directory so that people don't see it as a cgi-bin.&nbsp; Something like apps.mydomain.com or cgi.mydomain.com.&nbsp; This would allow for people to not be able to view the true directory structure to your cgi-bin (low grade security).&nbsp; In this case you could have all the cgi's running from a different site than your main page, so if the cgi's screw something up, the whole site won't go down.Hope that didn't sound like ramblings.Arnix (tm)</blockquote>

[QUOTE="Arnix, post: 323154, member: 5521"] You would also use a sub domain to seperate certain sections of your site, or to do distributed hosting (part of site on one web server, another part on another web server). If you had player info you could have players.mydomain.com instead of mydomain.com/players (a waste) or you could host player info off of a free site and have player.mydomain.com pointing to it, but maintaining you main site on the mydomain.com's host. This could help for bandwidth or speed issues. Split heavy traffic sections up on multiple cheap site with low bandwidth restriction and it will appear as one site, but using different bandwidths. You could also have a sub domain pointing to the cgi-bin directory so that people don't see it as a cgi-bin. Something like apps.mydomain.com or cgi.mydomain.com. This would allow for people to not be able to view the true directory structure to your cgi-bin (low grade security). In this case you could have all the cgi's running from a different site than your main page, so if the cgi's screw something up, the whole site won't go down. Hope that didn't sound like ramblings. Arnix (tm) [/QUOTE]

Verification