One more thing. With all that said, I'm not comfortable encouraging using MR3, unless you're ok with F#.
Btw, I'll be doing a presentation on MR3 Tuesday. Keep an eye at http://www.communityforfsharp.net/ On Sat, Aug 13, 2011 at 12:14 PM, hammett <[email protected]> wrote: >> 1. How ready it is for production? I know it has been asked already but I >> would like a more in-depth answer. > > All I can say is that we're using it in a very complex project that > should go online soon. We are very aware of a few to-dos and missing > features, and we're working on them as needed. > >> 2. What are the key differences between MR2 and MR3? Is there any MR3 or >> Blade quickstart/tutorial (or at least some kind of draft of such) > > The differences goes back to their goal. MR1/2 was a web framework. > MR3 should make your life easier if you want to deal with REST, and > compose applications from smaller apps. > >> 3. We will be using Spark, which we find much more productive than Razor, >> not to mention Brail or NVelocity. Would it be possible to use Spark with >> MR3? > > It depends on whether Spark supports closures/lambdas. > >> 4. Also what good reasons are there to use Blade and not Spark? > > The Helper API makes heavy use of lambdas. > >> 5. I've read on Hammett's blog about MR3's RESTfulness. We are looking >> forward to implementing REST services over our app in some way. Frankly we >> don't yet have any good idea how to best get it done with Monorail. How >> would it be done with MR3? > > Check the ContentNegotiatedResult [1], the serialization > infrastructure [2] and the hypertext processors [3]. Do you have > requirements you can share about the Restfulness of your website? > > [1] > https://github.com/castleproject/Castle.MonoRail3/blob/master/src/Castle.MonoRail/Mvc/Mvc.ActionResults.fs > [2] > https://github.com/castleproject/Castle.MonoRail3/blob/master/src/Castle.MonoRail/Mvc/Mvc.Serializers.fs > [3] > https://github.com/castleproject/Castle.MonoRail3/blob/master/src/Castle.MonoRail/Mvc/Mvc.Rest.fs > > > With regard to IoC Containers, it's a common misinterpretation. MR3 > does use MEF internally. It uses it at framework level. You app is > *not* running at the framework level, so it's completely independent. > At the moment we're using Windsor with our app, and it should be quite > easy to support others. > > > -- > Cheers, > hammett > http://hammett.castleproject.org/ > -- Cheers, hammett http://hammett.castleproject.org/ -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
