3 Here are a few ideas of tools, classes and projects that you
4 could start. More are forthcoming.
9 We need a verifier that can be run on an executable (assembly)
10 and tells whether the metadata for the executable is correct
11 or not. It should report any anomalies.
13 For a list of anomalies in assemblies, check the various assertions
14 that are described on the ECMA documentation.
16 This will help test our generated executables and can be also
17 used as an external verifier.
23 * Implement a JXTA protocol implementation:
24 <a href="http://www.jxta.org">http://www.jxta.org</a>
26 * Implement a Mail API, similar to Camel or JavaMail (Camel has
27 significant architecture features that are required on a real
30 You can check the current C
31 <a href="http://cvs.gnome.org/bonsai/rview.cgi?dir=evolution%2Fcamel">
32 Camel implementation</a>.
34 * Interfacing to Multimedia systems. You might want
35 to look into the Quicktime API. I know <a
36 href="mailto:vladimir@ximian.com">Vladimir</a> has
37 researched the problem before
44 * Implement an xmlStorageSystem for the CLI:
45 <a href="http://www.soapware.org/xmlStorageSystem">
46 http://www.soapware.org/xmlStorageSystem</a>
48 * Build a CORBA interoperability engine for the CLR.
49 You do not need to do all of the work, just talking
50 the protocol will get us a long way (<a
51 href="http://www.omg.org">The OMG site</a> has the CORBA specs).