<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Screencast: Alfresco Django integration</title>
	<atom:link href="http://ecmarchitect.com/archives/2009/06/11/1006/feed" rel="self" type="application/rss+xml" />
	<link>http://ecmarchitect.com/archives/2009/06/11/1006</link>
	<description>Jeff Potts on ECM, portals, search, collaboration, and a bunch of personal stuff</description>
	<lastBuildDate>Tue, 09 Mar 2010 23:10:06 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Django + Alfresco was a winning combination for retailer&#8217;s intranet &#124; ecmarchitect.com</title>
		<link>http://ecmarchitect.com/archives/2009/06/11/1006/comment-page-1#comment-43998</link>
		<dc:creator>Django + Alfresco was a winning combination for retailer&#8217;s intranet &#124; ecmarchitect.com</dc:creator>
		<pubDate>Thu, 05 Nov 2009 20:50:43 +0000</pubDate>
		<guid isPermaLink="false">http://ecmarchitect.com/?p=1006#comment-43998</guid>
		<description>[...] to use CMIS which is something we are considering for the open source version of the integration (Screencast, [...]</description>
		<content:encoded><![CDATA[<p>[...] to use CMIS which is something we are considering for the open source version of the integration (Screencast, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darren</title>
		<link>http://ecmarchitect.com/archives/2009/06/11/1006/comment-page-1#comment-36474</link>
		<dc:creator>Darren</dc:creator>
		<pubDate>Fri, 12 Jun 2009 17:30:57 +0000</pubDate>
		<guid isPermaLink="false">http://ecmarchitect.com/?p=1006#comment-36474</guid>
		<description>Thanks Jeff, that makes sense.

Personally I wish Alfresco could find a way to merge the two product lines.  There are elements of both that I&#039;d like to use on projects, and it&#039;s always frustrating to find out the feature that could help your project is only available on the other side of that fence.

+1 for AVM integration.</description>
		<content:encoded><![CDATA[<p>Thanks Jeff, that makes sense.</p>
<p>Personally I wish Alfresco could find a way to merge the two product lines.  There are elements of both that I&#8217;d like to use on projects, and it&#8217;s always frustrating to find out the feature that could help your project is only available on the other side of that fence.</p>
<p>+1 for AVM integration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jpotts</title>
		<link>http://ecmarchitect.com/archives/2009/06/11/1006/comment-page-1#comment-36471</link>
		<dc:creator>jpotts</dc:creator>
		<pubDate>Fri, 12 Jun 2009 15:55:56 +0000</pubDate>
		<guid isPermaLink="false">http://ecmarchitect.com/?p=1006#comment-36471</guid>
		<description>Darren,

Django communicates with Alfresco via web scripts. The web script API can talk to the DM repository and the AVM repository. So, if you wanted have your Django-powered site pull content out of the AVM store instead of the DM store you would start by changing the web scripts.

As to why we chose the DM over the AVM, the DM store is easier to work with. We use it by default unless someone has a specific reason to use the AVM store. As you mentioned, deployment might be one reason (although deployment is supposedly coming to the DM side of the house in a future release). Another reason would be to take advantage of sandboxes, layers, etc.

If there is significant demand for working with the AVM store we can bump that up in the roadmap.

Jeff</description>
		<content:encoded><![CDATA[<p>Darren,</p>
<p>Django communicates with Alfresco via web scripts. The web script API can talk to the DM repository and the AVM repository. So, if you wanted have your Django-powered site pull content out of the AVM store instead of the DM store you would start by changing the web scripts.</p>
<p>As to why we chose the DM over the AVM, the DM store is easier to work with. We use it by default unless someone has a specific reason to use the AVM store. As you mentioned, deployment might be one reason (although deployment is supposedly coming to the DM side of the house in a future release). Another reason would be to take advantage of sandboxes, layers, etc.</p>
<p>If there is significant demand for working with the AVM store we can bump that up in the roadmap.</p>
<p>Jeff</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darren</title>
		<link>http://ecmarchitect.com/archives/2009/06/11/1006/comment-page-1#comment-36434</link>
		<dc:creator>Darren</dc:creator>
		<pubDate>Thu, 11 Jun 2009 23:09:29 +0000</pubDate>
		<guid isPermaLink="false">http://ecmarchitect.com/?p=1006#comment-36434</guid>
		<description>Hi Jeff,

Nice screencast!

I&#039;m curious why you chose to integrate with the ECM portion of Alfresco, and not the WCM side?  It would be nice to be able to use the WCM deployment tools to be able to serve content from an Alfresco runtime, separate from the authoring environment.  I don&#039;t know if this is possible with the ECM functionality in Alfresco.</description>
		<content:encoded><![CDATA[<p>Hi Jeff,</p>
<p>Nice screencast!</p>
<p>I&#8217;m curious why you chose to integrate with the ECM portion of Alfresco, and not the WCM side?  It would be nice to be able to use the WCM deployment tools to be able to serve content from an Alfresco runtime, separate from the authoring environment.  I don&#8217;t know if this is possible with the ECM functionality in Alfresco.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
