.NET Best approach to implementing a client and server queue model with an external application?

Here is the specification:

  • Several clients using the winforms WPF application on their local machines
  • Clients initiate server requests to perform simulations. Perhaps this initiation should be through a web service, but other suggestions are welcome.
  • Requests are queued on the server
  • The server sends sequential requests for the simulation model through the web service.
  • The server tells the client that the simulation is complete.

An additional requirement is that the client cancel the request that they previously made. Please note that we do not need to worry about transferring too much data over the channel, we only send confirmation that the particular simulation run has completed (or failed)

For starters, I thought I could do all of this with one asmx web service, but now I think it can be cumbersome. WCF looks like another option, but I'm not familiar with it, and it seems much more complex than the functionality I need.

Any ideas?

+3
source share
4 answers

: , - . " -" - , . . " - .NET.

:. Web- vanilla.Net 2.0 asmx . , BackgroundWorker. . , . . BackgroundWorker.

. , , . CancelSimulation - , BackgroundWorker CancelAsync. , . -, /. , .

+2

WCF , , , .

WCF - , , , , (, - ).

, , , , ​​ MSMQ?

WCF MSMQ HTTP- SOAP , . REST - . , .

+1

WCF. - + ( ) - Twitter. WCF , .

, System.Messaging MSMQ. , MSMQ WCF, , . , . MSMQ, Windows.

, , . .

+1

You should take a closer look at WCF. I wrote a special library for work that takes care of some odd configurations, but you can write a great web service in a few dozen lines of code with WCF. It is very extensible. The only problem is that it will take some time to “get” it, but once you do it really, very simply. Good luck.

0
source

Source: https://habr.com/ru/post/1702897/


All Articles