svn commit: r879661 - in /websites/staging/stratos/trunk/content: ./ events/hangouts.html

[bu...@apache.org]

Author: buildbot
Date: Tue Sep 24 06:03:14 2013
New Revision: 879661

Log:
Staging update by buildbot for stratos

Modified:
    websites/staging/stratos/trunk/content/   (props changed)
    websites/staging/stratos/trunk/content/events/hangouts.html

Propchange: websites/staging/stratos/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Sep 24 06:03:14 2013
@@ -1 +1 @@
-1525796
+1525797

Modified: websites/staging/stratos/trunk/content/events/hangouts.html
==============================================================================
--- websites/staging/stratos/trunk/content/events/hangouts.html (original)
+++ websites/staging/stratos/trunk/content/events/hangouts.html Tue Sep 24 06:03:14 2013
@@ -127,49 +127,18 @@ display:none;
 <p style="padding-bottom: 50px;">With Apache Stratos now in the incubator phase, We wish to invite committers to join our Apache Stratos Hangouts, learn the architecture, follow the next steps of the project and help to decide the way forward to make this a successful project.</p>
 
 <div class="cHangoutContainer">
-<!--<div class="cHangout">
-<h2>Next Hangout - Discussion on RESTful API for Stratos Controller</h2>
-<span class="date" style="padding-bottom:0px; background: #ffffff; color: #07648d; padding: 0px;">Tuesday, 17th of September, 2013 - 7.30 AM (PDT)</span>
-
-<h3>Introduction:</h3>
-<p>At the moment, the Stratos admin interfaces are tightly coupled to Carbon admin services. Hence All the backend interfaces are exposed as web-services.  This in turn has encouraged developers to develop stratos controller front-ends as Carbon UI components.</p>
-<p>It is possible to develop Stratos backend interfaces as RESTful services. The initial proposal is to develop them as a seperate JAX-WS webapp. But the topic is open for discusssion. </p>
-<p>This would allow Stratos developers to,</p>
-<ul>
-    <li>Create front-ends (simple web-apps) that make use of restful APIs.</li>
-    <li>Commandline tooling can make use of REST APIs as well.</li>
-</ul>
-<h3>Following is the agenda:</h3>
-<ul>
-    <li>Carbon admin services and how frontend components interacts with them</li>
-    <li>Stratos controller API (existing) and its UI components.</li>
-    <li>What it takes to deploy a web-app in Carbon kernel</li>
-    <li>Accessing core OSGi services by means of CarbonContext API</li>
-    <li>JAX-RS web-app exposing admin services of Stratos - big picture</li>
-    <li>How Custom web-app frontend/command line tooling can interact with the deployed REST apis.</li>
-</ul>
-
-</div>
-
-<p>--&gt;
 <div class="cHangout">
 <span class="date">17th September</span>
-<h2>Discussion on RESTful API for Stratos Controller</h2></p>
+<h2>Discussion on RESTful API for Stratos Controller</h2>
 <h3>Introduction:</h3>
-
 <p>At the moment, the Stratos admin interfaces are tightly coupled to Carbon admin services. Hence All the backend interfaces are exposed as web-services.  This in turn has encouraged developers to develop stratos controller front-ends as Carbon UI components.</p>
-
 <p>It is possible to develop Stratos backend interfaces as RESTful services. The initial proposal is to develop them as a seperate JAX-WS webapp. But the topic is open for discusssion. </p>
-
 <p>This would allow Stratos developers to,</p>
-
 <ul>
     <li>Create front-ends (simple web-apps) that make use of restful APIs.</li>
     <li>Commandline tooling can make use of REST APIs as well.</li>
 </ul>
-
 <h3>Following is the agenda:</h3>
-
 <ul>
     <li>Carbon admin services and how frontend components interacts with them</li>
     <li>Stratos controller API (existing) and its UI components.</li>
@@ -180,7 +149,6 @@ display:none;
 </ul>
 
 <div class="cVideoContainer"><iframe height="220" src="//www.youtube.com/embed/VW1Chbd7DcA" frameborder="0" allowfullscreen></iframe></div>
-
 <!--<div class="cSlidecontainer"><iframe src="http://www.slideshare.net/slideshow/embed_code/25663023" height="220" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="max-width:427px;border:1px solid #CCC;border-width:1px 1px 0;margin-bottom:5px"> </iframe></div>-->
 
 </div>