Comments on: Roller leaves the nest http://ecmarchitect.com/archives/2007/05/04/749 Jeff Potts on ECM, portals, search, collaboration, and a bunch of personal stuff Mon, 14 May 2012 10:48:07 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: siddharth http://ecmarchitect.com/archives/2007/05/04/749/comment-page-1#comment-29297 siddharth Thu, 08 Jan 2009 09:43:48 +0000 http://ecmarchitect.com/archives/2007/05/04/749#comment-29297 Can u plz explain how have u integrated Liferay with Apache Roller 4.0 ? We want you to do the same. Can u plz explain how have u integrated Liferay with Apache Roller 4.0 ? We want you to do the same.

]]> By: John Newton http://ecmarchitect.com/archives/2007/05/04/749/comment-page-1#comment-3447 John Newton Wed, 23 May 2007 08:39:59 +0000 http://ecmarchitect.com/archives/2007/05/04/749#comment-3447 Sounds great. Maybe we can share the details of how the stack fits together in a podcast. Sounds great. Maybe we can share the details of how the stack fits together in a podcast.

]]> By: John Eckman http://ecmarchitect.com/archives/2007/05/04/749/comment-page-1#comment-3113 John Eckman Sun, 06 May 2007 17:06:11 +0000 http://ecmarchitect.com/archives/2007/05/04/749#comment-3113 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? 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?

]]>