Difference between revisions of "Summer of Code 2006"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Here are some project ideas for the [http://code.google.com/soc/ Summer of Code 2006] ... | |||
=== Distributed monitoring of the Jabber network === | |||
(proposed by Lucas Nussbaum - xmpp:lucas@nussbaum.fr) | |||
The Jabber network isn't really known for its reliability, and administrators don't always have the necessary tools to monitor their server correctly. The data provided by http://public.jabbernet.dk/mrtg/ is not enough. The goal of this projet is to build a testing framework to be able to monitor the public servers and answer those questions : | |||
* do client connections using SASL, TLS or SSL currently work on server S1 ? | |||
* do server-to-server works between server S1 and S2 (by exchanging ping <message/>s) ? | |||
This would allow to build a more detailed status of the Jabber network. Additionally, it would be nice to be able to add a contact email, so the administrator can get informed of his server's problems. | |||
Revision as of 17:58, 19 April 2006
Here are some project ideas for the Summer of Code 2006 ...
Distributed monitoring of the Jabber network
(proposed by Lucas Nussbaum - xmpp:lucas@nussbaum.fr)
The Jabber network isn't really known for its reliability, and administrators don't always have the necessary tools to monitor their server correctly. The data provided by http://public.jabbernet.dk/mrtg/ is not enough. The goal of this projet is to build a testing framework to be able to monitor the public servers and answer those questions :
- do client connections using SASL, TLS or SSL currently work on server S1 ?
- do server-to-server works between server S1 and S2 (by exchanging ping <message/>s) ?
This would allow to build a more detailed status of the Jabber network. Additionally, it would be nice to be able to add a contact email, so the administrator can get informed of his server's problems.