----- Original Message ----- > From: "Alissa Bonas" <[email protected]> > To: "Yair Zaslavsky" <[email protected]>, [email protected] > Cc: [email protected] > Sent: Thursday, March 7, 2013 5:31:03 PM > Subject: Re: [Engine-devel] Best place for new interfaces used by bll > > > > ----- Original Message ----- > > From: "Yair Zaslavsky" <[email protected]> > > To: "Alissa Bonas" <[email protected]> > > Cc: [email protected], [email protected] > > Sent: Thursday, March 7, 2013 8:27:23 AM > > Subject: Re: [Engine-devel] Best place for new interfaces used by > > bll > > > > > > > > ----- Original Message ----- > > > From: "Alissa Bonas" <[email protected]> > > > To: [email protected] > > > Cc: [email protected] > > > Sent: Wednesday, March 6, 2013 10:50:52 PM > > > Subject: Re: [Engine-devel] Best place for new interfaces used by > > > bll > > > > > > 1. For start, and since you are already refactoring :) I > > > recommend > > > putting the interfaces in package named "api" and not > > > "interfaces" > > > - > > > it's a much more standard name. > > > 2. Can you elaborate a bit more what area/functionality in engine > > > are > > > those interfaces for? It will reflect their location. > > > > Yes, we're working on modularization/refactoring/improving of the > > async task manager. > > Bll will be a consumer (depend on) of async task mgr. > > From going briefly over the packages in "common" module, it seems > that there are 2 types of code there- > code really in use by backend and frontend, and code used only by the > backend. > So part of the code residing there is not really "common". > My suggestion is to take out that non common code from "common" > (along with async task mgr which is also not common), and create a > new module (names - core? infra? ) on which only backend/bll will > depend.
Right. And then start splitting bll in by subject... and then split the interfaces by subject... and then merge the interfaces of specific subject with bll of specific subject. For example bll of host deploy should be maintained separately from bll of gluster etc... > > > > > > > ----- Original Message ----- > > > > From: "Ravi Nori" <[email protected]> > > > > To: [email protected] > > > > Sent: Wednesday, March 6, 2013 6:57:10 PM > > > > Subject: [Engine-devel] Best place for new interfaces used by > > > > bll > > > > > > > > Hi, > > > > > > > > I am working on refactoring some of the backend code in bll and > > > > need > > > > to > > > > create interfaces so that I can eliminate the dependency > > > > between > > > > bll > > > > and > > > > the new module. > > > > > > > > Currently I created the interfaces in > > > > org.ovirt.engine.core.common.interfaces, but from what I > > > > understand > > > > this > > > > module is used by both frontend and backend. The new interfaces > > > > will > > > > only be used by the backend. What would be the best place to > > > > put > > > > these > > > > new interfaces? > > > > > > > > Ravi > > > > _______________________________________________ > > > > Engine-devel mailing list > > > > [email protected] > > > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > > > > > _______________________________________________ > > > Engine-devel mailing list > > > [email protected] > > > http://lists.ovirt.org/mailman/listinfo/engine-devel > > > > > > _______________________________________________ > Engine-devel mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/engine-devel > _______________________________________________ Engine-devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/engine-devel
