: Is it correct to have domains with more than 3 levels? I've been arguing for some time about this topic, now I'd like the opinion of professionals. My point is that a domain should be made

@Gretchen104

There's nothing explicitly wrong with it. It's just a domain. It's as cumbersome as you choose to make it. Some legitimate concerns, however, would revolve around the testing of security and certificates, etc.

Since certificates are based on the TLD, it would be impossble to run tests against any web service that sits behind an SSL layer.

Similarly, cookies are also domain driven so it would be difficult to perform testing on cross domain applications unless there were explicit controls placed on the naming scheme. It isn't impossible, but it does become harder to manage.

Vote Up Vote Down

@Voss4911412

I don't necessarily agree that a domain always has to be short. It depends a lot of how it is used. Let's say you're an agency having to show multiple projects to multiple customers, but not all these customers actually do have domains of their own, so something like supercooldemo.customer.com will not always be possible.

So, you'll probably end up with something like this:

demos.agencysite.com/customer/supercoolproject/index.html


This isn't all that differed from

supercoolproject.demos.customer.agencysite.com/index.html


I'm not a systems export and don't know what kind of configuration efforts are required to manage different subdomains, but from a user point of view I don't think there is much different in defining a path in a "real" path or doing so using domains.

Vote Up Vote Down