According to CMS Wire, Java-based blog server Roller has graduated from the Apache incubator. At Optaros, we’re doing some work for a client right now that involves implementing Roller as one component of the company’s Enterprise 2.0 initiative. Their Enterprise 2.0 stack includes Liferay for portal/presentation services, Alfresco for portal content, documement, and web content management, Roller for internal and public-facing blogs, and Confluence for internal wiki.
So far, Roller has been relatively straightforward to integrate with Liferay, but in the initial phase we’re doing very light integration. It essentially involves skinning the Roller UI so that the experience will be fairly seamless as portal users move from the RSS portlet to Roller (for example, when they comment on a blog post). In a later phase we hope to implement a much tighter integration, perhaps through Roller-specific Liferay portlets.
I’ve long thought it would make good sense to break up the functionality generally provided by blog software into distinct interfaces – separate authoring, presentation, commenting, and moderation into distinct modules that can be run on different servers in different tiers.
Most blog software exposes the posting API out to the public when there’s really no reason for that. Of course you can password protect it and such, but why even have that authoring code running on a server in the DMZ?
Similarly, why not have the code that accepts comments in from end users running on a web-exposed machine, but have the moderation functions running in a separate execution environment?
This would allow better scaling of the pieces that scale faster and also better separate the security contexts of the applications.
Perhaps Roller’s a good candidate for this kind of approach?
Sounds great. Maybe we can share the details of how the stack fits together in a podcast.
Can u plz explain how have u integrated Liferay with Apache Roller 4.0 ? We want you to do the same.