Need Ideas For An Architecture
I am developing an application internally for my business unit.
Phase 1, will simply be a HTML5/ Responsive application that will essentially be used as a sales demo/ powerpoint that talks through our offering. This is fairly easy I will use HTML5 Js/Jquery to call on any server side functions and will use the sharepoint API and our sharepoint system to grab documents (pdf/ppt/word/ect).
The next part is what has me a little challenged.
What I would like to do is have the application use the Sharepoint API for a CDN. The application would have a function that checks connection to the API. If this is lost or if the network card is not connected to the internet then I would use a cached version of the application that would have limited functionality.
Thoughts? Coding this in MVC ASP.Net will be pretty easy. It is the caching offline that I am curious about. How would you go about building the application so that it does a weekly check to update all the Front-End content and then based on the offline/online function it will enable/disable UI components.
So in summary:
Thoughts?
Phase 1, will simply be a HTML5/ Responsive application that will essentially be used as a sales demo/ powerpoint that talks through our offering. This is fairly easy I will use HTML5 Js/Jquery to call on any server side functions and will use the sharepoint API and our sharepoint system to grab documents (pdf/ppt/word/ect).
The next part is what has me a little challenged.
What I would like to do is have the application use the Sharepoint API for a CDN. The application would have a function that checks connection to the API. If this is lost or if the network card is not connected to the internet then I would use a cached version of the application that would have limited functionality.
Thoughts? Coding this in MVC ASP.Net will be pretty easy. It is the caching offline that I am curious about. How would you go about building the application so that it does a weekly check to update all the Front-End content and then based on the offline/online function it will enable/disable UI components.
So in summary:
- Main application is HTML5 Frontend, Backend C# ASP.Net and uses the MVC pattern.
- It grabs information from Sharepoint via API.
- The user logins to the application using SSO or their Corporate credentials which will pass through with the API to allow the connection to sharepoint.
- If the application detects the system is offline it defaults to an offline cached version of the application and then uses the cached local code.
- At a specified period (most likely weekly) the application will try to connect to the main site and download any updates for the cache.
- The application needs to be stored in such a way that clearing the browser cache will not wipe the application
Thoughts?
Read my blog @ www.buildingautomationmonthly.com
Connect with me on LinkedIn @ https://www.linkedin.com/in/phillipzito
Connect with me on LinkedIn @ https://www.linkedin.com/in/phillipzito
Comments
-
philz1982 Member Posts: 978Apparently I should be able to use Application Cache and web storage. Has anyone used these? Does it get wiped when someone clears browser cache?Read my blog @ www.buildingautomationmonthly.com
Connect with me on LinkedIn @ https://www.linkedin.com/in/phillipzito