Add messaging url + fix other links

diff --git a/docs/developer/researchprojectspage/index.mdwn b/docs/developer/researchprojectspage/index.mdwn
index 8402acd..5f38246 100644 (file)
--- a/docs/developer/researchprojectspage/index.mdwn
+++ b/docs/developer/researchprojectspage/index.mdwn
@@ -21,10 +21,8 @@ Please feel free to add projects to this page, or annotate existing project idea
 * Optional versioning?
 * Potential uses: ... HAMMER, UFS, HAMMER mirror streams, message passing, ...
 * CAPS (DragonFly's message passing system, which exists but is not functional at the time of this writing) has an over-the-wire format with serialization/deserialization. This codegeneration serialization solution should be amenable to the purposes of CAPS or whatever future message passing infrastructure might be implemented in DragonFly.
-* CAPS References: [1](http://www.shiningsilence.com/dbsdlog/2003/11/25/139.html#more-139
-) [2](http://www.shiningsilence.com/dbsdlog/2004/03/07/293.html#more-293
-) [3](http://www.shiningsilence.com/dbsdlog/2004/04/24/365.html#more-365
-)
+* CAPS References: [1](http://www.shiningsilence.com/dbsdlog/2003/11/25/139.html#more-139) [2](http://www.shiningsilence.com/dbsdlog/2004/03/07/293.html#more-293) [3](http://www.shiningsilence.com/dbsdlog/2004/04/24/365.html#more-365)
+* Messaging References: [1](http://leaf.dragonflybsd.org/mailarchive/commits/2006-07/msg00172.html)
 
 ### Asynchronous system call framework
 * Probably best implemented as a message passing interface to kernel pass messages in, threads pick them up and execute, return through kevent notifications