Thanks for the info Amareshwari, Should we explore if we can have a single conf for Lens encapsulating both client and server confs, Or, Having a lens conf and client/server have their specialized confs.
Best regards On Mon, Aug 3, 2015 at 9:45 AM, amareshwarisr . <[email protected]> wrote: > Yash, > > LensClientConfig : Creates a client configuration and provides helpers > methods to set/get configuration properties. > LensServerConf : Provides static getters for accessing lens server > configuration. > LensConf : Is a transport object, holding a map, for clients to send > configuration over REST. > > Right now, there are no relations between LensClientConfig, LensServerConf > and LensConf classes. > > They are independently added in different modules for some functionality > related to configuration. > > Thanks > Amareshwari > > On Sat, Aug 1, 2015 at 11:52 AM, Yash Sharma <[email protected]> wrote: > > > Hi All, > > I see that there are multiple Conf's in codebase - LensClientConfig & > > LensServerConf. > > > > And there is LensConf which is not extended by either. Should we not > have a > > super type for all LensSpecific confs. And the implementations can add > > specific stuffs. > > > > Thoughts ? > > >
