Rain Framework

01/19/12 - 07:03 PM

Ben Hanna

I'm always looking to minimize code-inclusion in my projects and Rain Framework seems to give me a lot of the basic structure of an MVC application (DB, session, and stuff like that) while still allowing me to write most of my own code. I do have some concerns though. In looking through some of the code, I've noticed that some classes seem more coupled than others. For example, the User class is hard-coded to depend on the Rain_User class (which could be easily overridden) which depends on a certain database schema to store and authenticate users. There should definitely more extensibility in user authentication because one project I'm planning on doing here is one that would authenticate against an LDAP directory. My inclination here is to rewrite the User implementation using an interface in which different classes will independently dictate how authentication takes place.

I've already forked the repository for making the aforementioned changes as well as integrating RedBean (which is painfully easy).

Other than that, I think the framework shows a lot of promise. Keep up the good work.

02/09/12 - 12:07 AM

Rain
Rain Team

Hey Ben,

the first version of the framework was first released in 2007, recently we entirely re-wrote the framework and released in 2010 as version 2.0. The Rain Framework is basically new and we're still working to make it better, that's why some classes are coupled differently. Soon we will release Rain CMS http://www.raincms.com and Rain TPL 3, in alpha version on github https://github.com/rainphp/raintpl3 and the next step it will be the Rain Framework 3.0.

Thanks for your positive feedback, in particular thanks for your critic, because help us to do better!

You are also invited to contribute on the rainframework code, github it's very easy and fun:
https://github.com/rainphp/rainframework

Thanks.