I have to say, complete WCF support is not realistic. Nor is important. We'll still live with small subset of it. Especially I don't see huge need for WS-* anymore. It is much more important to get lower level HTTP,TCP and some derivatives (such as WebHttpBinding) stable. That's what I have been working on these months.
Atsushi Eno (2011/04/19 13:15), jmalcolm wrote: > The roadmap for Mono 3.0 lists the following as the major features: > > - New Generational GC becomes the default > - IKVM Reflection or Cecil powered C# compiler > - SGen: Precise stack scanning > - New profiler > - Tuned Parallel Frameworks > - Complete .NET 4.0 Core Support > - Complete WCF 4.0 API support > - Tail call optimizations for F# > - MonoMac and MonoMac bundler > - IronPython, IronRuby and F# bundled with Mono > > If I am correct, the following features are already present in 2.11 > (master): > > - IKVM Reflection or Cecil powered C# compiler > - SGen: Precise stack scanning > - New profiler > - MonoMac and MonoMac bundler > - IronPython, IronRuby and F# bundled with Mono (in 2.10) > > What is the status of the following? > > - New Generational GC becomes the default > - Tuned Parallel Frameworks > - Complete .NET 4.0 Core Support > - Complete WCF 4.0 API support > - Tail call optimizations for F# > > The reports I have been seeing are that the GC is very close. I see quite a > lot of chatter about WCF support so I assume that is coming along as well. > How are the parallel and tail call projects coming? The last I heard, there > was nobody working on tail call optimisation. > > > -- > View this message in context: > http://mono.1490590.n4.nabble.com/Mono-3-0-tp3459389p3459389.html > Sent from the Mono - General mailing list archive at Nabble.com. > _______________________________________________ > Mono-list maillist - [email protected] > http://lists.ximian.com/mailman/listinfo/mono-list > > > _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
