does it make sense changing site to subdomain ?

lets say my site is located at www.mysite.com/private - and already registered with search engines

does it make sense to register it as a subdomain as www.private.mysite.com ?

I mean all the links will continue to work, its just that it looks more profesional in my opinion.

I think awhle back it did but now most people do not care or even know the difference. You used to see it a lot on commercials using the sub-domain but now more & more are just using the folders.

I believe it depends on the content of the site in question. If your data is stored in many different sub folders then it can make things easier.

Lets for example imagine that you have the following folder:

http://www.mysite.com/services/host...bers/joebloggs/

You can make this easier to access by either setting up virtual directories or by setting subdomains. Virtual directories are ok so long as you don't have a folder of the same name as the root. The above could be simplified to:

www.mysite.com/joebloggs

Virtual directories don't have to be based in the root directory they can be in other folders. Sub domains would solve the problem of long URL's in a similar way to the above, but would make it easier because they have to be unique.

ok I understood that.

now another question connected to the first one:

my site is located at: www.mysite.com
I use dto access it via ftp and the root of my site was the htdocs folder. in this fodler I have index.html severall folders which stand for subdomains and the /cgi-bin folder.

Now while installing different cgi scripts I have frequently read the term non-public-space I asked my provider about this and he told me that I could make a directory called site and redirect my domain into this folder. So everything outside this fodler would be non-public.

But how would I best structure the site: should I leave the cgi-bin directory outside the site fodler or should it go inside it?

I have a access.pl file in my cgi-bin folder which displays my access log and shows me the way visitors took while visiting my site. I would like to protect access to this file. I have made a html file which links to this access.pl file and lies in a access-restricted folder so in order to access the html file one must enter a password and only then can one click on the link to the access.pl. but what if somebody entered www.mysite.com/cgi-bin/access.pl ??? he will get access to my logs.

Would the above mentioned restructuring help prevent this? And if I leave cgi-bin outside the /site folder how does a lonk from my html page to access.pl look like? I have been using links relative to site root so far. Do I have to change my links to be relative to the document? Anyway which method of linking is preferable?

Hears a helpful hint for anyone reading this. Don't access the posts your subscribed to using hotmail. It messes with your log in status so messages cant be posted. This is my second time of writing this.

When you install a web server, such as apache, it creates a folder called htdocs. This contains all of the files that are available in to the public viewing your site, as you know. It also creates a folder in the same folder that contains the htdocs folder called cgi-bin.

As this folder is outside of htdocs it should be unavailable to the public, in theory if not in practice. I must admit I don't use CGI a lot so I don't have a great amount of knowledge about how to execute scripts from this directory, but I'd would have thought it was pretty straight forward. The configuration file for the server also specifies this directory as the default script location, so this should make it a lot easier.

If you can't get this to work you can place them elsewhere and use a .htaccess file to restrict access to the directory as execute only or whatever. They can also be used to allow access from specific IP addresses only, so this could help prevent others executing them. Try searching google for the full list of things they can do.

The only other thing I can suggest if this don't help is to go post a thread in the CGI/ Scripting forum whatever its called.

ok, thx so far

as the post took totaly another direction I opened a new post in a more fitting category. Read further development of the discussion here