Another thing to keep in mind is clearly separating the simple API &
extensibility APIs. For example, if you take Clustering, sending messages,
getting the member list and so on are the "simple" APIs. The interfaces for
defining a new clustering implementation should be part of the advanced API
(in this case, it is the advanced clustering SPI). Another example would be
the deployment component. Calling it to trigger deployment, getting
deployment data/stats would be part of the simple API, and defining new
deployers would be part of the advanced API.

Azeez


On Wed, Nov 6, 2013 at 5:21 AM, Afkham Azeez <[email protected]> wrote:

> I am starting a new thread to further discuss what came up in "C5 - Carbon
> Deployment Engine".
>
> As part of the C5 effort, we need to clearly define the external APIs for
> all major functionality we provide, and also clearly document it. This
> needs to be followed from day 1 itself. These interfaces need to be
> discussed on architecture@ before finalization.
>
> This practice has to start from the kernel, and then has to be adopted by
> all major components.
>
>
> Thoughts welcome.
>
> --
> Afkham Azeez
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
>
> email: [email protected] cell: +94 77 3320919
> blog: http://blog.afkham.org
> twitter: http://twitter.com/afkham_azeez
> linked-in: http://lk.linkedin.com/in/afkhamazeez
>
> Lean . Enterprise . Middleware
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* <http://www.apache.org/>*
*email: **[email protected]* <[email protected]>
* cell: +94 77 3320919 blog: **http://blog.afkham.org*<http://blog.afkham.org>
*twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
* linked-in: **http://lk.linkedin.com/in/afkhamazeez
<http://lk.linkedin.com/in/afkhamazeez>*

*Lean . Enterprise . Middleware*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to