in order to speed up web page loading times, manage resources etc, I want to server some of my resources from subdomains so and want to understand how actinic treats the use of images contaning the http:// tags
I also recognise that I start stepping out of the "actinic safety net", and I become 100% responsible for moving/maintaining/deleting images from my sub domains, the trade off being a much faster verification/checking/upload process when refreshing the site - again, outside the "actinic safety net" - its a trade off I am prepared to accept
let me explain.
within the actual main page layout, its easy to have code such as <img src='myimage.jpg'>, taking that a stage further, I can use <img src='http://images/mydomain.com/myimage.jpg'> and serve all those images from the subdomain.
taking it to the third level, I can then introduce an actinic variable to the tag and generate code like <img src='<actinic:variable name="CompanyDomainImages" />/myimage.jpg'> allowing me to copy the entire site to another place, change the odd actinic variable and then have everything pointing to images on images.anotherdomain.com - this for multi user sites, may be quite an advantage.
this "works" fine but I now need to understand how the "internal upload to the web" process works. - using the following programming choices
how does the internal upload process work ??-
I then want to take this a stage further and move some of my main product images to a subdomain.
so within the layouts, you see <img src="<actinic:variable name="ProductImageFileName" />"
I want to change that to <img src="<actinic:variable name="CompanyDomainForImages" />/<actinic:variable name="ProductImageFileName" />" . . .
if I adopt a similar approach as show above, how does the internal parser/upload process handle those.
can anyone help please
kev
I also recognise that I start stepping out of the "actinic safety net", and I become 100% responsible for moving/maintaining/deleting images from my sub domains, the trade off being a much faster verification/checking/upload process when refreshing the site - again, outside the "actinic safety net" - its a trade off I am prepared to accept
let me explain.
within the actual main page layout, its easy to have code such as <img src='myimage.jpg'>, taking that a stage further, I can use <img src='http://images/mydomain.com/myimage.jpg'> and serve all those images from the subdomain.
taking it to the third level, I can then introduce an actinic variable to the tag and generate code like <img src='<actinic:variable name="CompanyDomainImages" />/myimage.jpg'> allowing me to copy the entire site to another place, change the odd actinic variable and then have everything pointing to images on images.anotherdomain.com - this for multi user sites, may be quite an advantage.
this "works" fine but I now need to understand how the "internal upload to the web" process works. - using the following programming choices
- <img src='myimage.jpg'>
- <img src='http://images/mydomain.com/myimage.jpg'>
- <img src='<actinic:variable name="CompanyDomainForImages" />/myimage.jpg'>
how does the internal upload process work ??-
- tries to find myimage.jpg on the local server and uploads it as part of the refresh process
- assumes you've put the right url in, and generates code accordingly but DOES NOT try to upload anything from the local server as part of the refresh process
- what happens here, I know it generates the correct url code for me, but does it still try to look for the image on the local server like option 1, ignore the image like 2, or just gets its knickers in a twist??
I then want to take this a stage further and move some of my main product images to a subdomain.
so within the layouts, you see <img src="<actinic:variable name="ProductImageFileName" />"
I want to change that to <img src="<actinic:variable name="CompanyDomainForImages" />/<actinic:variable name="ProductImageFileName" />" . . .
if I adopt a similar approach as show above, how does the internal parser/upload process handle those.
can anyone help please
kev
Comment