asynchronous - Background tasks/timer jobs in SharePoint O365 with Azure provider-hosted app -
I am creating a provider-hosted app for SharePoint (O365) which is hosted in Azure. Through all of my arguments, I am using a MVC Web project more specifically. At the moment, I have some branding logic that is being executed by an application after an AJAX call in a controller action.
If there are so many subsites in my hierarchy, it can take a very long time to execute because it is bad because the app will still process my request, the page I called This action would prevent me from reacting to the completion of the work. This is definitely because the request status is directly related to the callback of that request in the calling page. It also means that a person can launch the request, refresh the page, and then launch it again, because there is no way to tell me that any previous request is still being executed Yes or No. In addition, 2 different users can launch the same request, resulting in 2 simultaneous executions of the logic of that request.
So, what I need is a way to see if a specific request is already going on, and if it is not, then both situations can be the reason. Launch the one that is stateful and asynchronous. The best example I can think is that just long-running work mechanics of SharePoint O365: launch time-intensive tasks (such as installing apps or creating a new site archive) from a page , And then refresh or access to that page, display the ongoing work, sometimes giving it the possibility to cancel it (such as an app In Nstol). The state will also be updated on its own (such as when a site collection is created), which I do not know is the result of client side polling or any other mechanic I do not know.
I have seen some solutions that looked promising, like using it or, although no one fulfills all the requirements listed above and / or what I want to implement I feel compliance for I think timer jobs can potentially help, but I wanted your advice on the situation.
Thanks for your input
Try using the ezu worker role Hosted with CSOM and a SharePoint provider's side-loading tenant full control permissions Side loading part enables your worker to read / write SharePoint Online.
Side loading is done through /_layouts/appregnew.aspx and _layouts / appinv.aspx.
Comments
Post a Comment