Pooling works with AsyncCallback(s).
Pooling works with AsyncCallback(s).
All Callbacks are pooled through a delegate void using the System Thread Pool, manual work is queued by ThreadPool.QueueUserWorkItem..
Creating threads on there own is not pooling & never use thread.sleep its a bad habit, instead use a timer with a timer call back and reset events against the pool to perform timed work, a timer on its own uses the thread that spawned the timer and not the pool so don't get confused by this.
smtp update: Its now possible to use TLS.
So every smtp server should work even hotmail(tested).
I'm making sockets better without pooling, and mysqlreactor better without pooling. You will see. SocketHandler will hold up to 100,00,00 users <3.
Good Luck with it :)
Posted via Mobile Device
Joopie Make groups and homes, and when the two go out? Emu and CMS? Forecast?
Some code:
Rights - Pastebin.com
Nah, doubt that. Having 10E6 users is a unrealistic number. With this large amount there are other considerations which needs attention, like the database and network capacity. I don't think the .NET platform can support this much users. And if you are using non-async sockets, you are going to get a huge lagg, since then the server has to wait for the data to be sent instead of moving it to the threadpool ;)
Those application which users non-async sockets are most likely server applications which is only ment for one user. New platforms like Silverlight does not support non-async sockets to avoid lagg in the UI-Thread. Read more of this on MSDN if you are in doubt :)
- Martin
Im currently busy with FriendStreaming, seems good.
---------- Post added at 01:07 PM ---------- Previous post was at 12:17 PM ----------
Finished
![]()