On Tue, Mar 18, 2014 at 8:47 PM, Sanjiva Weerawarana <[email protected]>wrote:
> However that does not change the validity of Nuwan's mail .. the notes > were not very useful at all! > > Folks these notes are CRUCIAL because a lot of people are not in the room > when a given discussion occurs. The notes have to capture the spirit of the > discussion along with sufficient detail for someone not in the room to get > a good sense of what was discussed. Yes its not easy - neither is what we > do. > +1 > > Shameera please send an updated set of notes - you were not there when > Azeez, Sameera, Pradeep and I chatted near the fish tank .. so please send > a better summary of what was discussed (I wasn't in the room so I don't > know what you guys considered either). > > Nuwan my suggestion was to question the assumption that we MUST have an > admin UI (and hence framework) to the extent we had in C4. > Well IMO we need to have an admin UI. Its not a must to bundle and ship with the server runtime, but if someone needs the UI (s)he should be able to install the UI to the runtime. The runtime MUST have an API (REST) which we already building, so the UI can use this API and provide the admin functions. In that way the API will also be properly designed / implemented and the POC for that will be the UI. Regards, /Nuwan > > Sanjiva. > > > On Tue, Mar 18, 2014 at 8:10 AM, Afkham Azeez <[email protected]> wrote: > >> Immediately after this meeting, some of us had a casual chat with >> Sanjiva, and we had a concern whether we need the management console at all >> because we don't see it being used in production. I will send a separate >> mail about that. >> On Mar 18, 2014 2:08 AM, "Nuwan Bandara" <[email protected]> wrote: >> >>> Hi Shameera, >>> >>> This meeting minutes are not descriptive enough nor they are clear about >>> what conclusions were made, what are the next steps are to be taken etc. >>> Please send a descriptive version of meeting notes as C5 UI framework an >>> important item and am sure everybody would like to contribute. We also need >>> to look at current limitations of the Carbon UI framework and how to >>> address them in the rewrite. >>> >>> Regards, >>> /Nuwan >>> >>> >>> On Mon, Mar 17, 2014 at 2:38 PM, Shameera Rathnayaka >>> <[email protected]>wrote: >>> >>>> Hi Pubudu, >>>> >>>> >>>>> - By default disable HTTPS transport >>>>> >>>>> It should be HTTP, not HTTPS >>>> >>>> >>>> Cheers, >>>> Shameera. >>>> >>>> >>>>> - OSGI services - stale reference >>>>> - The behavior of a service that becomes unregistered is >>>>> undefined. Such services may continue to work properly or throw >>>>> an >>>>> exception at their discretion. >>>>> - Therefore to prevent potential problems, Bundles must >>>>> listen to events generated by the Framework to clean up and >>>>> remove stale >>>>> references. >>>>> - Tenant aware security manager ? >>>>> - UI level permissions ? Authentication and Authorization >>>>> - Read-only access for all Worker nodes >>>>> >>>>> >>>>> - Sameera >>>>> - Can jaggery run as a bundle in jetty ? >>>>> - isolation of UI bundles or are we going to copy relevant file >>>>> to specific directory ?, Ruchira suggest isolation is a good choice >>>>> - How alternative servers handle UI frameworks ex : JBoss >>>>> - Tomcat connectors ? >>>>> - Product.xml - Model is yet to be finalized ( Jaggery >>>>> extensions suggestion by Pubudu ) >>>>> - Ruchira >>>>> - current model of jaggery keeps all necessary files within a jar >>>>> - Isolation so it will be easy to perform installation and >>>>> uninstallation >>>>> - component.xml can be replace with component.json - Model is >>>>> yet be finalized >>>>> - Rino runtime provides security for jaggery >>>>> - Allow apps to be use REST endpoints >>>>> >>>>> >>>>> Cheers >>>>> P.S Feel free to add any missing points >>>>> >>>>> -- >>>>> *Pubudu Dissanayake* >>>>> Software Engineer >>>>> WSO2 Inc.; http://wso2.com >>>>> lean.enterprise.middleware >>>>> Mobile: 0775503304 >>>>> >>>> >>>> >>>> >>>> -- >>>> *Software Engineer - WSO2 Inc.* >>>> *email: shameera AT wso2.com <[email protected]> , shameera AT >>>> apache.org <[email protected]>* >>>> *phone: +9471 922 1454 <%2B9471%20922%201454>* >>>> >>>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 >>>> *Twitter : *https://twitter.com/Shameera_R >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> >>> >>> *Thanks & Regards,* >>> * Nuwan Bandara | Technical Lead - Solutions Architecture, WSO2 Inc.+1 >>> 812.606.7390 <%2B1%20812.606.7390> | +1 650.745.4499 Ext 4210 >>> <%2B1%20650.745.4499%20Ext%204210> | http://nuwanbando.com >>> <http://nuwanbando.com> * <http://www.nuwanbando.com/> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: [email protected]; office: (+1 650 745 4499 | +94 11 214 5345) > x5700; cell: +94 77 787 6880 | +1 408 466 5099; voip: +1 650 265 8311 > blog: http://sanjiva.weerawarana.org/; twitter: @sanjiva > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Thanks & Regards,* * Nuwan Bandara | Technical Lead - Solutions Architecture, WSO2 Inc.+1 812.606.7390 | +1 650.745.4499 Ext 4210 | http://nuwanbando.com <http://nuwanbando.com> * <http://www.nuwanbando.com/>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
