On 25.01.2009, at 22:58, Guoliang Cao wrote:
> With that being done, current merb will become merb-core + merb-web + > merb-more. Any comments? Some parts of Merb, like abstract controller and bootloaders, may be useful outside of front end web apps. Even with simplest EventMachine daemons or Nanite agents this sort of framework (dispatcher + possibly rendering capabilities) is reinvented by every developer one way or another. However, merb was built for web and used for web, I'd leave merb-core/ merb-more as is. If you have any specific ideas, please elaborate. For instance, I have extracted class loader to use with Nanite, and I have ideas to extract bootloaders into separate library, but I have no idea what are your needs :) MK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
