[Sigia-l] URLs and brands

[Travis Wilson]

If you accept that the majority of users are just gonna browse company.com 
anyway, and navigate from there (to new domains or within the same domain), 
you may want to consider the pragmatic issues too. Do some groups want to 
run their own webservers? If company.com only runs Apache to serve static 
files, and group 1 needs a dynamic back end (say to do user profiling or 
database-driven pages), you can't really push the slash concept onto them.

company.com/group1 and company.com/group2 are both served by the same 
webserver, whereas group1.company.com and group2.company.com may be served 
by different webservers running on different OSes in different parts of the 
world. Sometimes, this is important.

trav

At 08:12 PM 11/15/2002 -0500, Beth Mazur wrote:
>We've been pushing the slash concept, you know:
>
>company.com/group1
>company.com/group2
>company.com/group3
>
>Our rationale is that most people only think company name, so they'll
>probably just type company.com and then navigate from there anyways.
>
>Some of our departments would prefer doing the unique domain, like:
>
>companygroup1.com
>companygroup2.com
>companygroup3.com