<?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: Recommended Architecture for custom Web App in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/recommended-architecture-for-custom-web-app/m-p/286141#M239271</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Some uses expose Alfresco Share.&amp;nbsp;&amp;nbsp; Should not be too much of a problem.&amp;nbsp;&amp;nbsp;&amp;nbsp; Its unlikely a "hack" will be enabled.&amp;nbsp;&amp;nbsp; For one the open source software gets a lot of eyes looking at it, reporting bugs and testing.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Or you can go for a wcmqs based app.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Or you can write your own front end with a tool of your choosing with alfresco as a back end.&amp;nbsp;&amp;nbsp; Which is the most common option.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 18 Jun 2015 14:20:40 GMT</pubDate>
    <dc:creator>mrogers</dc:creator>
    <dc:date>2015-06-18T14:20:40Z</dc:date>
    <item>
      <title>Recommended Architecture for custom Web App</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/recommended-architecture-for-custom-web-app/m-p/286140#M239270</link>
      <description>Hi,We are building a Custom web-App for Document/Project Management and Collaboration purposes. This application will be accessed on internet.Most of our requirements are addressed by Alfresco-Share. Can we customize Alfresco-Share client (UI as well as components) and expose it to end-users over in</description>
      <pubDate>Thu, 18 Jun 2015 10:26:09 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/recommended-architecture-for-custom-web-app/m-p/286140#M239270</guid>
      <dc:creator>naval</dc:creator>
      <dc:date>2015-06-18T10:26:09Z</dc:date>
    </item>
    <item>
      <title>Re: Recommended Architecture for custom Web App</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/recommended-architecture-for-custom-web-app/m-p/286141#M239271</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Some uses expose Alfresco Share.&amp;nbsp;&amp;nbsp; Should not be too much of a problem.&amp;nbsp;&amp;nbsp;&amp;nbsp; Its unlikely a "hack" will be enabled.&amp;nbsp;&amp;nbsp; For one the open source software gets a lot of eyes looking at it, reporting bugs and testing.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Or you can go for a wcmqs based app.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Or you can write your own front end with a tool of your choosing with alfresco as a back end.&amp;nbsp;&amp;nbsp; Which is the most common option.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Jun 2015 14:20:40 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/recommended-architecture-for-custom-web-app/m-p/286141#M239271</guid>
      <dc:creator>mrogers</dc:creator>
      <dc:date>2015-06-18T14:20:40Z</dc:date>
    </item>
  </channel>
</rss>

