asp.net of the annex



  • There's asp.net an annex-coacher with multiple sources. The answer is about 200 ms each. Hundreds of bands are already in 20 seconds, and they may be hundreds. We have to do this on the background, that's not when the user went on the site. In the background, data will be collected and maintained in the OBD system, for example. The user, coming to the site, just gets them from the OBD. Question: How to make the annex work without the user? Something has to trigger the code, which in the timer, for example, will do business. As an option, a 24-hour micro application to the domestic PC, which makes a request to the main annex. Multi-point helps, but still the processing time is very big - don't offer it.



  • I agree with the view that we should do the service.

    But the logic may be different, so the service can hammer everything in a row, but the relevance of the data will be very delayed.

    It is possible that the service be given an assignment to calculate specific data. Then, from asp.net of the application, we give the task to the service and not to wait until the timemaouth gives us the answer that the request was formed and retrieve request, further when the service completes its task, it signals the client.

    Information can be provided in a variety of ways, if, after completion of the task, the service will be able to record in b.d. and javaScript every 5 to 10 seconds, to engender the outcome of the task previously received by the id.


Log in to reply
 


Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2