Blogs : Latest entries
|
|
|
Update: RIFE 1.0 has been announced on The ServerSide and a nice discussion is going on there, join us! After four years of development and seventy releases, we finally consider RIFE to be feature-complete. The project has come a long way over the years and the goals have been constantly re-evaluated against production projects and newly introduced technologies. RIFE is now running on sites with 300000 daily page views, it is used for critical systems in a leading telephony company and has scaled down to embedded usage in mobile phones. We have also developed several other open-source projects with it like a forum (Bamboo), a blog (Elephant), an information bot (Drone), and a to-do list tracker (Bla-bla List). Below are the highlights:
You can also read the full changelog for more details. Congratulations and many thanks to everyone who contributed to make this milestone happen. |
|
RIFE has been licensed under LGPL for quite a while because I want to have the developer protections that it offers (ie. changes have to be released as open source under the same license). Sadly, there has been much controversy about LGPL's usefulness in Java projects. There also seems to be a consensus that LGPL projects will never be used in commercial products due to the doubt and uncertainty that surrounds it. Finally, Apache seems the have major problems with LGPL and takes a long time to make up their mind about it. So I'm considering relicensing RIFE under another license which offers the same kind of developer protection but is not shunned for commercial usage. The candidates seem to be CPL, MPL or CDDL. The first one has Apache's blessing and the last two will soon be accepted for binary inclusion in Apache projects. I quite like the sound of CDDL, but there seems to be a lot of FUD around it. The connection with Sun doesn't seem to be liked by many, but it seems like the merely tried to improve MPL. What are your thoughts about CDDL, is it a good choice for an open-source Java web application framework or should I look for something else? Are other licenses with the same developer protection worth considering? |
|
The G-team released Groovy version 1.0-jsr03 yesterday. I've been anticipating this release for quite a while, since they managed to fix all the bugs that prevented correct integration of Groovy into RIFE. I'm very pleased that the upcoming RIFE 1.0 release will fully support Groovy everywhere and that everything is ready to make the first release of RIFE/Crud with Groovy support too.
Thanks a lot G-team! |
|
For the upcoming release of RIFE 1.0, we finally wrote and designed a dedicated project website at rifers.org. It is close to being finished and I'm happy that we'll at last not just be a generic project on java.net anymore Tell us what you think! |
|
Since RIFE is soon to hit version 1.0, I decided to go over the available servlet containers again and noticed that tagtraum silently released version 1.1 of jo! which supports version 2.3 of the servet spec. What I like about this servlet container is that you can run it with or without a Swing GUI. The GUI is very handy since you can very easily experiment with your setup and immediately have access to all the log files. You can even deploy WARs by simply dragging and dropping them on the windows (doesn't seem to work on MacOSX yet). This is the full feature list:
Give it a try when you're developing your next web application. |
.
A few years ago I was quite excited by