Our (old) College website hosted some collections of assets (like images/logos), styles (CSS), scripts, XML library (XSLT stylesheets, XSD schemas); along with data feeds, web services, configuration files and so forth.
Each of these resources/services could be used beyond the website itself, referenced from other websites or documents (for example: an XSLT date conversion function; a default CSS stylesheet that could be imported and selectively overridden by various websites; an EMF logo for a Word template).
In some cases, the appropriate protocol would be http, in others https. The resources would generally be publicly-accessible except those that made changes to data or had performance impacts on our systems.
What might be good practice in the hosting of shared resources? How might these disparate libraries be best managed?
Tavis Reddick
Web Developer
Adam Smith College
The information contained within this e-mail is confidential and may be privileged. It is intended for the addressee only. If you have received this e-mail in error please inform the sender and delete this e-mail and any attachments immediately. The contents of this e-mail must not be disclosed or copied without the sender's consent.
The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the author's employer (the College). The College does not take any responsibility for the views of the author.
Adam Smith College, Fife, is a registered Scottish charity, No: SC021196
|