| |||||||||
|
|||||||||
[Home] [Overview] [Status] [Todo] [Releases] [Sourceforge] | |||||||||
  | |||||||||
  | |||||||||
OverviewThe Debugserver project is one which attempts to make the process of development and the eventual debugging of an application as painless as possible. It provides a facility to remotely log debugging information ready to be analysed using a web broswer. It will also provide remote administration so that old debugging information can be deleted to reserve disk space and maintain performance of the system. The actual server is coded in Java. The language was chosen for
a number of reasons. The main reason is that using sockets and
threads is very easy in Java compared to C/C++. Another, more
selfish reason is that I wanted to brush up on my Java programming
skills.
| |||||||||
  | |||||||||
Current StatusCurrently, the project is on release 0.2. In this release, there is the server, two client APIs and a simple command-line client implementation. The server logs the information to file where it can be viewed via the HTTP implementation. The two clients provide an easy to use connection to the server. At the moment there exist two client APIs; one for Java and one for C++. | |||||||||
  | |||||||||
TodoThe next job to be completed will be the viewer implementation. This will include specifying the connection protocol and writing server and client sides. Another one is to introduce connection controls into the server. This includes selecting address-ranges to block/allow, an account based control (admin must set up an account with password before client can connect), automatic house-keeping (deleting expired information), etc. The admin connection protocol also needs to be completed and implemented. This could be built upon the viewer protocol. | |||||||||
  | |||||||||
| |||||||||
  | |||||||||
[Home] [Overview] [Status] [Todo] [Releases] [Sourceforge] | |||||||||
  |