CodePudding user response:

This doesn't make much difference whether and thread,

CodePudding user response:

Mainly is to monitor the rabbitMQ consumers and consumption of these two operations,
You can join in the Global file Application_Start directly to monitor initialization, so you can over a period of time continue to receive messages,
Because IIS timing recovery, so when you initialize the set up to monitor will be recycled, so you need to call it,
So general rarely in the web side for message consumption, most in the console program or Windows service to listen,

CodePudding user response:

Continuous pushed from the server to the client; You can take the HTTP connection or WebSocket way long,

CodePudding user response:

Every thing has its own structure, webapi service, it is very simple, it won't go to the polling or blocking, client access webapi moment is to obtain the return value, so its mechanism itself is far from "continuously receives the message,"

CodePudding user response:

Like a function call the function b return value, you can imagine at this point "how to keep the b receives a request", this kind of problem is completely a originally is a function of their concept to disturbed, architecture design is not here, the news about the actual system of mechanism design, is not this kind of design, here is the title party,

CodePudding user response:

Registered in the applicaiton. You start consuming events...

CodePudding user response:

Do you have solved the problem of the webapi? Please let