C# asynchronous server architecture?

Question

C++ / C#

Looked at a lot of different code, incl. on www.google.com/codesearch , but I didn’t understand for myself how to separate the business logic of the server from the server part itself? Is it really possible to process incoming data in the ReceiveCallback method by a case? And if you need to make queries to the database, wait for a response, compare it with the data received from the server, and then only send the result to the user?

How is the processing logic organized directly on an asynchronous server? Can books what are specialized for C#?

Answer 1

As I understand it, the task is in writing an application server and in the actual implementation of the logic?
In this case, the application server will only have the task of providing transport and “hosting” the business logic module, which, in principle, should not know anything about the application server.
Can you clarify the question a little? What technologies do you use? What version of .NET?
Are you using WCF, WebServices, or some other communication channel?
Perhaps the processing of "long" requests in separate threads will help, which, after the completion of the calculations, will notify clients that it is possible to "take the result"?

Answer 2

Maybe this will help msdn.microsoft.com/en-us/library/fx6588te.aspx