M
Mauricio Morales
Guest
The idea is the following.
I have a service in .NET framework 4.6.1 which executes some methods from the different classes, basically the methods are realted to extract, insert and update data of a Progress Open Edge database for a billing module.
Besides there is a controller which calls this method which is called by a front-end build in angular 4.x.
So the idea is to don't allow a final user to call the controller, through the front-end, to start the process again, and don't have an error of timeout or something like that in the front-end. Also could be fine to see a progress bar or something to tell the final user that there is a billing task in process.
In advance, thank you so much.
Continue reading...
I have a service in .NET framework 4.6.1 which executes some methods from the different classes, basically the methods are realted to extract, insert and update data of a Progress Open Edge database for a billing module.
Besides there is a controller which calls this method which is called by a front-end build in angular 4.x.
So the idea is to don't allow a final user to call the controller, through the front-end, to start the process again, and don't have an error of timeout or something like that in the front-end. Also could be fine to see a progress bar or something to tell the final user that there is a billing task in process.
In advance, thank you so much.
Continue reading...