Home

Features

Besides inheriting most of the feature set of ServerChecker v3 this release comes with new features:

• ServerChecker V4 can take control of server software that is already running before ServerChecker starts.
• ServerChecker V4 can run as a windows service.
• ServerChecker V4 has remote control capabilities. It also supports multiple users with different access levels. Remote control is both encrypted and authenticated.
• It supports different levels of trust for code. e.g. a ServerChecker Plugin may not have the same permissions on the running system as ServerChecker itself. ServerChecker V4 itself is supposed to require as few permissions as possible. Serverchecker V4 is also designed to minimize influence of one subsystem to another.

Known bugs in the initial source code release

As with all software ServerChecker has some known issues:

• Remoting connections are set up quite often, rather than once per session. This can cause slowdowns when operating the GUI.

Work to be done

The initial source code release is a work in progress and cannot be seen as a finished product:

• Keys embedded in the project are to modified.
• Licensing code may be stripped out altogether since this is rather incompatible with the GPL License (unless everyone is granted a license by default).
• The GUI was originally seen as a test application for the back-end. It has superseded that goal during development and as such it may have various weaknesses and design flaws.
• The GUI will require updates of the references to the ServerChecker V4 client library.
• a lot of finishing, testing...

Future enhancements

ServerChecker v4 currently uses .NET Remoting. Technology has evolved and there are other ways to do the same thing, like WCF.