The development server is required for the CVS installation and organization of the development process. Also the latest version of the software will be available here for the tests. This version will have it's own license and it's own id for the auto-update server.
The auto-update server is required for the changes and licenses distribution to the clients hosts. The changes are distributed by the client host request. The client host is authenticated by the IP, ID and password.
In most of the cases the client will connect to the auto-update server in the random time and receive all of the changes from the CVS system as a diff patch. The times and results of the patching is stored on the auto-update server.
The same way the client server will receive the licenses for the modules.
Generally this server shouldn't be very powerful, but should have the fast internet connection.
Generally this server should be power enough for the required amount of the clients. One client requires will take about 5-10 sec on up to date single processor machine. Since the client should receive the patch between two dates (two versions) of the software, and this operation will load the HD, it's possible to say that only one connection per time is possible.
The checkout should be received for the auto-update domain by cron (one per day will be enough).
05 * * * * cd [path to csv]; chmod -R 777 ./; cd [path to auto update part]/checkout; cvs -d [path to csv] checkout ./ >> /dev/null 2>&1; chown -R [apache user of the auto-update domain]:[apache group of the auto-update domain] ./;
If the development server and the auto-update server are different - the path to csv should contain all of the required information for the development server access. In most of the cases the auto-update server should be authenticated by the certificate.