![]() I can see the temp queue being created after the GetTempQueueName() call. ![]() Var message = new Message(loginResponse) Transaction = "Here is your response data" ![]() Var loginResponse = new StateLoginResponse() and eventually a response is queued up like so: using (var mqClient = ResolveService().CreateMessageQueueClient()) This message is received on the normal queues. MqClient.Publish(queueName, new Message(new StateLoginRequest() We publish the original message like so: var tempQueue = mqClient.GetTempQueueName() I don't like the asynchronous nature of the system we are using, but there is nothing we can do about it (it's what we… The MQ server then does it's thing, picks up the message, logs things, sends requests to other systems, and our UI polls looking for responses that were logged.īut now we need to implement kind of synchronous communication for some specific processes (logging in to state services, over an asynchronous flow). So far we've only worked with one way messages (publish and forget). MqClient.Get - Does it handle listening for specific responses, or do we need to?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |