Currently, we always ship the clients and Admin services in one pack, so if we change one we automatically get the other.
Do we have a usecase where we need clients and admin services are separate? I think this make sense for those cases only. For example, BAM should be able to receive events from multiple versions of the WSO2 products ( it is not a admin service though, just an example). --Srinath On Mon, Apr 6, 2015 at 9:28 AM, Jayanga Dissanayake <jaya...@wso2.com> wrote: > Hi Prabath, > > Great idea, > > This will loosen the dependency between the admin service and the admin > service clients. So the admin services can evolve easily, as new features > come under a different version tag and existing functionalities are not > effected. > > But we have to have some policies to control that new additions, Those > should be only, > 1. Improvements > 2. New features that aligned with the original purpose of that admin > services > Otherwise everyone will try to add/improve admin services with different > different features and finally endup as totally different 'hybrid' admin > service, with bunch of functionality that are not related to each other. > > And there should be some system to keep version details of admin services. > Everyone using those admin services should update to the latest service > ASAP. If not we will have to face the very same problem we currently have > with bundles. > > Thanks, > Jayanga. > -- ============================ Blog: http://srinathsview.blogspot.com twitter:@srinath_perera Site: http://people.apache.org/~hemapani/ Photos: http://www.flickr.com/photos/hemapani/ Phone: 0772360902
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
