Of course you can have Analog just exclude items from your reports that you don't want to show, e.g. REQINCLUDE PAGES, so creating separate domains for each type of file may not be necessary. It could also complicate reporting if you have media that is hard to qualify -- where do you put a PDF file?

I think that most companies who set up separate domains do so to get the most out of the right configuration for each type of media. So if you have dynamic pages, you want to serve those out of the proxy fronting your application and data servers, and your static images or video/audio you may host from a large data center where bandwidth is cheaper (e.g. akamai).

One of the problems that I could foresee in splitting domains would be SSL. If you have secure sections on your web site, you want to have all content on those page (pages, images, flash) under https or the browsers may complain or block the non-secure content. This would require you to have SSL certs for each subdomain. I have no idea if this would affect performance at the client end, but I think it could increase your cert management overhead significantly.

--
Jeremy Wadsack
Seven Simple Machines



Walter Ian Kaye wrote:

I'm not sure if this is OT or not....

I was thinking to have a nice clean "page" log I'd put all my image, audio, and video resources in a subdomain. Anyone else here do this?
I've seen subdomains like:
audio.*
video.*
image.*
media.*
I'm kinda leaning towards media.*. Thoughts?


+------------------------------------------------------------------------
|  TO UNSUBSCRIBE from this list:
|    http://lists.meer.net/mailman/listinfo/analog-help
|
|  Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
|  List archives:  http://www.analog.cx/docs/mailing.html#listarchives
+------------------------------------------------------------------------

Reply via email to