Analyze the effects of hosting the xml schema only on the web tier.

[GoogleCodeExporter]

Currently, the xml schema is housed in the web tier code under static 
resources.  All code must obtain the schema via url call, the effect of which 
may result in performance degradation.

Also, the web tier will be a key point of failure and must be continually 
available or else we won't be able to process scenes.

Consider moving the schema to espa-common, deploying espa-common to 13.  Or.  
Consider deploying espa-common to nginx and having nginx serve up the schema 
out of espa-common.  

That way the code can rely on the local file path and not the webserver but the 
schema will still be globally available and version controlled.

Original issue reported on code.google.com by davehil...@gmail.com on 14 Jul 2014 at 7:52

[GoogleCodeExporter]

Original comment by davehil...@gmail.com on 29 Jul 2014 at 2:44

• Added labels: Milestone-2.5.0, Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

back end processing and science code is working off the xsd in espa-common.  
This issue is tied to espa issue 241.

Original comment by davehil...@gmail.com on 7 Aug 2014 at 2:05

• Changed state: Started

[GoogleCodeExporter]

this is done, requires testing.

Original comment by davehil...@gmail.com on 18 Aug 2014 at 5:07

• Changed state: Fixed

[GoogleCodeExporter]

verified

Original comment by davehil...@gmail.com on 1 Oct 2014 at 3:42

• Changed state: Verified