looking good. I`m sure i will test it
Printable View
looking good. I`m sure i will test it
use visual C# express 2008 to open itQuote:
Originally Posted by sontung306
I have a recomendation for your project
Everyone ever involved on server maintenance and deployment is used to have "Services" running.
Those Services have some advantages:
- windows resources priority
- security (login account) can be especified
- what to do in case of services shoot down
- system login of each event
- RPC (windows security protected)
and a very long list of extra positive things so developers use to release mission critical and long term server based tools compiled as "windows services".
So why not you?
The main problem will be "support" on how to install and remove a windows service, but install/uninstall classes can be coded inside the exe so people can attach/dettach the service from the OS as a optional feature.
U whant me to help with this?... just let me know
wolfulus can you DC a client from the CS if you want to ?
if you code it, yes you can, but the current code is a console application, without interface... just a tray icon, with a "hided" console window...Quote:
Originally Posted by sandbird
maybe on future updates... i'm not thinking about these things now, just wanting to get it fully functional :]Quote:
Originally Posted by FT1FT1
yeah, bad english, i know, sorry ;D
Another advice:
Working with a fixed count of connection slots is not resource wise.
if you are going to work that way you must at least let the server manager to chose how many connections allow as a parameter so your line:
become:Code:private DtClient[] Clients = new DtClient[100];
I will recommend the use of thread pools instead of fixed countCode:private DtClient[] Clients = new DtClient[globalVariableMaxConnections];
Another Project Started by me one year ago coded in C++ if your wanna try here is SVN Repository https://opensvn.csie.org/DareEMU/
thansk a lot . usefull
thanks a lot