If you look at most products, the only reason event component is there is for publishing BAM messages. As per yesterday's discussion, having the entire event component is overkill, and it does not work anyway when there is a high load. So, for Stratos we have to fix this. Removing something that does not work will be good for the release. This will reduce our product sizes by quite a bit too.
On Sat, Jun 4, 2011 at 5:44 PM, Amila Suriarachchi <[email protected]> wrote: > > > On Sat, Jun 4, 2011 at 11:50 AM, Afkham Azeez <[email protected]> wrote: > >> Sanjiva, Shankar & I had a discussion yesterday, and it seems that having >> the event feature in most components is just overkill. Also, in Stratos, >> QPid causes the server to go out of memory when we do load testing because >> BAM tries to publish events, this will make all our services unstable hence >> one of the most critical L1s. Sanjiva mentioned that Hiranya had developed a >> bit of lightweight code for publishing these BAM events, and we could use >> that. Apart from BAM, only deployment synchronizer uses this feature in the >> case of the services such as AS, ESB etc right? >> > > No. All the components which uses event use the new this event API and > hence all those projects require Qpid. But in the event design point of view > it is possible to use an registry based implementation instead of Qpid on > those products and shift the Qpid based implementaion only with MB and CEP. > > But I am realy concern about the time line we have to do such a drastic > change. > > thanks, > Amila. > > >> >> -- >> *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* >> * >> * >> *Lean . Enterprise . Middleware* >> >> >> _______________________________________________ >> 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 > > -- *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* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
