Hi, I'm about to start developing the C++ based command-line server admin client. There's still an open question (as far as I know) as to its relationship with other packages.
My opinion currently is that the client should be in a separate repository and available as a separate package for the following reasons: 1. The client will depend on libtpproto-cpp, which is not required by tpserver-cpp, and libtprl, which will no longer be required by tpserver-cpp once my changes are merged. 2. The client could be used with other servers which choose to implement the remote admin protocol. 3. Other clients may be used to administrate tpserver-cpp (notably, the upcoming single-player mode in tpclient-pywx, whose typical user probably has no interest in a CLI client). 4. The server and client might reside on separate machines. 5. The server does not even strictly require an admin client, as it can be controlled by signals and configured on the command line or by the config file. If we assume the average user of tpserver-cpp will want local CLI client functionality, essentially how it works now with the console, then we could provide a "full" tpserver-cpp bundle which includes the client (and its dependencies) and a "minimal" tpserver-cpp bundle which is just the server itself. (I think this is more or less what Lee was suggesting off the list.) Thoughts? -- Aaron Mavrinac www.mavrinac.com PGP Public Key: http://www.mavrinac.com/pgp.asc _______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
