First off, very good article, very interesting and something I hope to utilise
soon so thanks :)
The one question I do have is:
What if you have users who, when editing content in the browser decide they
want to add an image from their personal hard drive to the content? The image
will display correctly for them because the reference in the HTML points to the
location on their pc where the image file is stored.
BUT what about other users who then try to access the same content ? They wont
see the image because they dont have the image stored locally?
Hi Jake
First off, very good article, very interesting and something I hope to utilise soon so thanks :)
The one question I do have is:
What if you have users who, when editing content in the browser decide they want to add an image from their personal hard drive to the content? The image will display correctly for them because the reference in the HTML points to the location on their pc where the image file is stored.
BUT what about other users who then try to access the same content ? They wont see the image because they dont have the image stored locally?
Any thoughts on this ???