Welcome to CP!
Christian_V_V wrote:
The source code is in this link: http://www.mediafire.com/file/kze3zztjzve/httprequest.rar\[^\]
This is not how CP works. People hardly download code. You can post the relevant code here and ask about doubts.
Christian_V_V wrote:
There will be hundreds of entries per minute
There are many things to consider when implementing a highly scalable server application. Few of them are,
How much users will be connected simultaneously? If this is more than 50, you are better off with asynchronous methods. It allows to create highly scalable applications. If you have less number of users, asynchronous methods will add unnecessary complexity to your program.
Are you starting new thread for each client? If yes you will run into problems. You need to use a ThreadPool. I have once written a highly scalable server with a custom thread pool taken from Smart Thread Pool[^].
From my experience, I found it is best to work directly with Socket class rather than the wrapper class like UdpClient.
If you need to keep reference to the clients that are connected, you should consider using a data structure that will allow faster searches. In .NET, Dictionary class is good and it allows searching in O(1).
You will find this[^] MSDN article helpful.
Christian_V_V wrote:
Also, if i need multithread in the database part.
Databases are already multi-threaded. What do you meant by that? :)
Navaneeth How to use google | Ask smart questions