Loading Shop Images from a SubDomain makes a lot of sense, Pagetesters like
"http://tools.pingdom.com" will 'thank you' for this with a much better 'overall perfomance Result.'
If you use different 'SITE URL's', but only under the SAME MAIN 'Customer Server DIRECTORY', it makes even more sense to CALL the IMAGE URL from another Site-URL, as shown below. This way, you reduce the LOAD of the Shop Server URL even more, compared with just calling the IMAGES from the same basic URL, by USE of the "http //www .SHOP-Server. ccc/image/" Address.
Still, if you have only ONE SITE URL registered within the same (YOURSITE) Server-Directory, DO IT ANYWAY, it will increase Speed in any Case, compared to the DEFAULT OC-Way, i.E.:
("http //www .SHOP-Server. ccc/image/")
'grabbing' it's images from their really OWN 'Place' and trough their OWN 'Lines' and 'Channels', so, not requiring to 'share' the Tasks with the 'Shop' Software itself, building the Page...
Many Internal Server Program Files are routed and loaded 'INTERNALLY', just like when you search for an Image on your local harddisk. Some other 'Routines' have to be 'EXECUTED', as deFacto Runtime Program, then, usually, an EXTERNAL HREF Internet based Call may be requested, to make it work. This, in very short, and very lowdown, the difference between HREF Links and INTERNAL Paths...
This is a typical regular Image 'HREF' URL-CALL, by use of this Mod, calling a Site like:
Assortment of Files, related:
or, if you only have ONE SIte, registered on that specific Server and it's Main Site Directory:
as Alternative, next Best to a really 'separate' Way of doing it. It's better than nothing, because it will DOUBLE the tasks of the Browsers, trying to built the Page out of the Content delievered...
Compared with, as it would look like, if used the regular 'www' way:
If I call a related Shop Page like:
then, this is a REGULAR 'internal Directory-Path' Image-CALL, by use of DEFAULT 'Link-Values':
And this is the 'internal Directory-Path' Image-CALL, by use of MODIFIED 'Values':
If a Subdomain-Call directs to the same 'Place' as the Shop, the DEFAULT PATH Values will will be used, as mentioned above in the REGULAR Dir-Path Description.
...trying to make it a bit more transparent...
YOU HAVE TO MAKE SURE, all images related to the Shop will be placed in the REMOTE Image Folders, if you PLACE the Image-URL into an other SITE-URL. Otherways, your image-'Handler' will not display and/or 'handle' all images related.
You NEED to operate multiple Servers under the SAME ADMIN accessable Server Path, to make it work under different URL's. THIS, because you need to set PATH's and URL's, and it's not possible for a Server to 'catch' DATA from another Server, on the same Server, but Location and Files placed in an 'outside' Customer Server Path'. I hope, someone understands, what I mean..., and I hope to be 'right' with this as well...
This is a typical INTERNAL Server PATH to the MAIN Image SubDir, in contrary to an URL:
Every Site, hosted under the 'YOURNAME' Main Directory, would be 'usable' to store and later call your images.
In the ZIP File enclosed, you find 3 Images, explaining, where TEXT has to be modified/quoted/deleted (whatever you chose), and added as well. SInce it would be of no use, I have not 'printed' the Config-File Commands anywhere, since they would not match your configuration anyway...
Your load time results will be:
70-85 percent images from http://images... Server
15-30 percent data from http://shop... Server.
Good Luck, I tried to cover it in full...
Remarks to the Image Below Subdomains / Aliases:
Sometimes, Sub-Domains are named WEBSITE ALIAS as well, just to avoid Confusion.
Your Server Admin Console should usually allow you to to set them up by yourselfs.
If setting up an ALIAS, you just DIRECT it's PATH to the Server ROOT, where your OC-Shop Main index+config.php files are located. The 'forwarding' to the Images File Directories works the same as by default, 'starting' the Paths from MAIN FILE ROOT as well.
Edited by Ernst Jakob, 04 June 2015 - 07:02 PM.