I've previously outlined my vision on where I think we should start aiming MR towards, see http://groups.google.com/group/castle-project-devel/browse_thread/thread/2c77d17327488889
Since then, I have prototyped something really simple on top of the existing MR code, have a look at http://github.com/johnsimons/MonoRail.Play This prototype is all based on what I described, turning requests into WebCommands and then have handlers that execute based on WebCommand (similar to what NServiceBus does), and since then I scratch the idea of executing these commands in parallel. But as you can see from the prototype code, I reckon to implement something so out there as what I'm proposing it has to be done from a green fields project. I'm also a big fan of making roles more explicit, what I mean by this is things like Filters in MR, which are for example used to enforce Authorization, I much rather have an AuthorizationFilter instead of a generic one. Anyway, looking forward to the other thread. Cheers John ________________________________ From: hammett <[email protected]> To: [email protected] Sent: Sun, 18 July, 2010 10:27:08 AM Subject: Re: Monorail's Future Before writing a single line a code we should agree on the direction/vision/goals. I'll start another thread. On Sat, Jul 17, 2010 at 4:02 AM, John Simons <[email protected]> wrote: > Hamilton, please do prototype something, that would be really nice. > > Cheers John > > On 17/07/2010, at 1:30, hammett <[email protected]> wrote: > >> I'm biased, but I'd favor extensibility. One - if not the - key factor >> for Windsor success is its extensibility. I'd like to see MonoRail as >> a minimal core with strong extension points. An user can "put >> together" a flavor of MR that meet his needs. Extensions work >> side-by-side. I'd love to prototype something along these lines if the >> idea resonates with the rest of you. >> >> And yes, I agree with Henry. It should be compatible with MVC - which >> is not difficult. >> >> >> >> 2010/7/16 Henry Conceição <[email protected]>: >>> I totally agree that we should have very clearly and well defined mission >>> and must be focused on it. And that we should not play catch with Ms. >>> >>> I think that productivity is still valid, but the magnitude have changed. In >>> the past was a webforms x mvc comparison, but today we have many tools that >>> are good as monorail is. >>> >>> Another great change imo, is that today we have an ecosystem towards mvc on >>> the .Net land. We can reuse existing view engines, routing engines, binders, >>> etc if we want to. >>> >>> On Jul 15, 2010 9:50 PM, "hammett" <[email protected]> wrote: >>> Exactly. >>> >>> So going back to the original theme. I'd invite you to step back and >>> see the whole picture. I see asp.net mvc as a quite successful >>> *blessed* solution from MS. I also see Fubu MVC and possible others >>> offering different perspectives on this space. >>> >>> I dont do web development anymore - unfortunately - but I dont think I >>> would be totally happy with MS' offering or MonoRail. >>> >>> asp.net MVC: >>> - has a great end-to-end experience (Fx + VS Integration + templates) >>> - Framework is quite minimal, which is a good thing >>> - Not very extensible IMO >>> >>> MonoRail >>> - Very extensible >>> - Has everything + the kitchen sink (bad) >>> - Bad end-to-end experience >>> >>> Instead of trying to play the catch up game I'd go for a totally >>> different route. >>> First. define the mission and vision. Since the beginning MonoRail was >>> about productivity. Does this still make sense? What has change in >>> this space? Are projects simpler or more complex? What about the >>> cloud? >>> Second, features should make sense for the vision, and this should be >>> your bar. Simply dont invest time/energy in whatever deviates from the >>> mission. >>> Third, end to end: what makes the tool successful is not only the Fx, >>> but samples, templates and VS integration. I have quite some >>> experience with VS, and could certainly help here. >>> >>> >>> Thoughts? >>> >>> >>> 2010/7/14 Henry Conceição <[email protected]>: >>> >>>> You're right about both affirmations. Imho, on the next version, the >>>> core should contain only th... >>> >>> hammett >>> http://hammett.castleproject.org/ >>> >>> -- >>> >>> You received this message because you are subscribed to the Google Groups >>> "Castle Project Developmen... >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Castle Project Development List" 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-devel?hl=en. >>> >> >> >> >> -- >> Cheers, >> hammett >> http://hammett.castleproject.org/ >> >> -- >> You received this message because you are subscribed to the Google Groups >>"Castle Project Development List" 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-devel?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups >"Castle Project Development List" 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-devel?hl=en. > > -- Cheers, hammett http://hammett.castleproject.org/ -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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-devel?hl=en. -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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-devel?hl=en.
