Thank you Angus,
Very good answers :)
A little bit more...
What kind of database you did use?
There will be one or two servers with around 250 clients each and I was
thinking of TCP/IP protocol
Is this what you have done?
Can communication be protected with blowfish? or do you have better
suggestions?
-daniel
----- Original Message -----
From: "Angus Robertson - Magenta Systems Ltd" <[email protected]>
To: <[email protected]>
Sent: Monday, November 30, 2009 6:31 PM
Subject: Re: [twsocket] Server & Client application
I have server which receives info from the clients (info like:
logs, hardware status, process status etc.). Server will also
disribute installation files and content to the clients.
Clients will be connected to the server all the time and will send
info (info like: logs, hardware status, process status etc.).
Clients will also check if there are new updates/files and will
download the files if there are new files. Clients will be capable
of receiving files from the server when the server sends the files.
I wrote such a suite of applications a few years ago, three servers and
500 clients.
Now, What components from ICS I do need?
Many of them, depends on protocols you choose.
Do I need to have some kind of database?
Almost certainly, my database had 100 tables and expanded by five gigs
per month, although a lot of information was purged each month as well.
Is it possible to protect the communication somehow?
Various ways.
What are my options? Can I succeed with ICS?
Yes, it's been done already. But only for an experienced developer,
maybe a team depending on time scale, a lot of careful design and
redundancy is required.
Angus
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
