<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Alfresco CMIS Usability in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-cmis-usability/m-p/308323#M261453</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'm not exactly clear about what you are asking for. Are you asking for a comparison of CMIS versus the old Alfresco native Web Services API? If so, I would offer a few bullets:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; - The old Web Services API is not being actively developed. All work in this area is currently in CMIS.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; - CMIS has multiple bindings. One is Atom Pub. The other is Web Services. So if you really need to continue using Web Services, use the Web Services binding with CMIS.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; - When you learn the CMIS API you are investing in a skillset that applies to future projects with Alfresco but other CMIS compliant repositories as well. The native Web Services API is proprietary to Alfresco.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Things to put in the plus column for the native Web Services API are:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; - There may be some API calls that CMIS does not cover. In those cases, you may have to use Web Services.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; - Some older integrations rely on it (PHP SDK, for example)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Soon, we will have the same public API that is available for Alfresco in the cloud running in Alfresco on-premise. When that happens, the preferred order of API use for on-premise will be:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; - Public API&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - CMIS&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - Public lifecycle web scripts&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - Custom web scripts&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - Internal lifecycle web scripts&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - Native Web Services API&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Jeff&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 15 Aug 2013 23:24:02 GMT</pubDate>
    <dc:creator>jpotts</dc:creator>
    <dc:date>2013-08-15T23:24:02Z</dc:date>
    <item>
      <title>Alfresco CMIS Usability</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-cmis-usability/m-p/308322#M261452</link>
      <description>Dear All!I am preparing a document which needs a comparative study between CMIS and Web Services.I need to support my usage of CMIS over Web Service in Alfresco . I need some points where i can emphasize this point.Kindly guide me for itThanks</description>
      <pubDate>Wed, 14 Aug 2013 07:00:12 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-cmis-usability/m-p/308322#M261452</guid>
      <dc:creator>rutaveejshah</dc:creator>
      <dc:date>2013-08-14T07:00:12Z</dc:date>
    </item>
    <item>
      <title>Re: Alfresco CMIS Usability</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-cmis-usability/m-p/308323#M261453</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I'm not exactly clear about what you are asking for. Are you asking for a comparison of CMIS versus the old Alfresco native Web Services API? If so, I would offer a few bullets:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; - The old Web Services API is not being actively developed. All work in this area is currently in CMIS.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; - CMIS has multiple bindings. One is Atom Pub. The other is Web Services. So if you really need to continue using Web Services, use the Web Services binding with CMIS.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; - When you learn the CMIS API you are investing in a skillset that applies to future projects with Alfresco but other CMIS compliant repositories as well. The native Web Services API is proprietary to Alfresco.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Things to put in the plus column for the native Web Services API are:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; - There may be some API calls that CMIS does not cover. In those cases, you may have to use Web Services.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; - Some older integrations rely on it (PHP SDK, for example)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Soon, we will have the same public API that is available for Alfresco in the cloud running in Alfresco on-premise. When that happens, the preferred order of API use for on-premise will be:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; - Public API&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - CMIS&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - Public lifecycle web scripts&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - Custom web scripts&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - Internal lifecycle web scripts&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; - Native Web Services API&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Jeff&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Aug 2013 23:24:02 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-cmis-usability/m-p/308323#M261453</guid>
      <dc:creator>jpotts</dc:creator>
      <dc:date>2013-08-15T23:24:02Z</dc:date>
    </item>
  </channel>
</rss>

