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

Reply via email to