On Mon, Feb 21, 2011 at 3:10 PM, Srinath Perera <[email protected]> wrote:
> Participants: Samisa, Azeez, Senaka, Amila, Srinath, Tharindu, Anjana, > Sumedha .. > > Reason for this meeting is to discuss problems while clearly > integrating eventing with registry, BAM, DS and others as discussed in > this thread. > > Usecases > 1. Registry, BAM and DS want to send out well formatted (non-xml) messages > 2. Users want to receive matching events for subscriptions hourly, > daily, or weekly instead of instantaneously > 3. MT support > > Out of them #1 eventing impl has to support > We agreed that we need to support #1 and #2, by providing components > that support those features so that all the products can reuse that. > > Also we agreed that changes have to be backward compatible to the users > > Currently carbon has dependency on two carbon event versions (without > considering ESB eventing support) and we want to move all components > to new eventing version. Plan is > > 1. Amila and senaka to discuss the scenarios > Done. And, I mailed the scenarios to architecture@. Let's make that the basis of the architecture review, [1]. [1] http://wso2.markmail.org/thread/kks4fnvog2h5vrow Thanks, Senaka. > 2. Come up and review the architecture > 3. Do a hackathon to fix all the products > > On Tue, Feb 15, 2011 at 9:38 PM, Amila Suriarachchi <[email protected]> > wrote: > > > > > > On Tue, Feb 15, 2011 at 9:32 PM, Afkham Azeez <[email protected]> wrote: > >> > >> > >> On Tue, Feb 15, 2011 at 9:21 PM, Amila Suriarachchi <[email protected]> > >> wrote: > >>> > >>> If the registry has a critical release in march I think the better > >>> solution is to move the old event implement modules to registry it self > and > >>> keep it there until they have time to migrate to new API. > >>> > >> What are the implications of different products of the same Carbon > >> platform version being dependent on different eventing APIs? > > > > I can discuss this on monday. As I understood Registry does not use the > old > > event API just as a pub/sub broker. But BAM and DSS use like that so the > > changes we need to make is trivial. > > > > thanks, > > Amila. > >> > >> > >> _______________________________________________ > >> Carbon-dev mailing list > >> [email protected] > >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >> > > > > > > _______________________________________________ > > Carbon-dev mailing list > > [email protected] > > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > -- > ============================ > Srinath Perera, Ph.D. > Senior Software Architect, WSO2 Inc. > Visiting Lecturer, University of Moratuwa > Member, Apache Software Foundation > Research Scientist, Lanka Software Foundation > Blog: http://srinathsview.blogspot.com/ > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2, Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://www.linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
