Hi Rajeev, We can divide databridge components into a two separate parts as server and client. AFAIK at the moment server part only used by BAM and CEP. But I think client part might need to all other wso2 products since we are going to create toolboxes for all of them. So IMHO is we can keep those client components in the carbon-commons and we can create separate git repo for the databridge server related components.
WDYT? Regards, Gihan On Wed, May 7, 2014 at 10:56 AM, Rajeev Sampath <[email protected]> wrote: > Hi, > > Currently part of the data-bridge (core components) are in carbon-commons > and the rest is in carbon-analytics. However there are arguments that > carbon-commons is not the right place to have these data-bridge components. > > Completely moving this to carbon-analytics doesn't seem to be a good > option either since quite a few products depend on this and they will have > to wait for a carbon-analytics release when there are updates. > > Do we need a separate git repo for data-bridge? Or else a better place to > move this? > > > Thanks > Rajeev > > -- > Rajeev Sampath > Senior Software Engineer > WSO2, Inc.; http://www.wso2.com. > > Mobile: > * +94716265766 <%2B94716265766>* > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- W.G. Gihan Anuruddha Senior Software Engineer | WSO2, Inc. M: +94772272595
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
