Hi Rasika, +1, I assume in the default configuration we will keep both these values to false since by default we would not need the publish info to DAS. Also, when you say publish operation response, does it mean we are publishing all operation info such as application list, device info and policy responses? If it's only device info, naming the config to PublishDeviceInfoResponse would make more sense IMO.
Regards, Inosh On Mon, Jan 22, 2018 at 12:36 PM, Rasika Perera <[email protected]> wrote: > Hi All, > > In IoT Server v3.1.0 geo location services is enabled with the following > configuration; > > <GeoLocationConfiguration> > <isEnabled>true</isEnabled> > <PublishLocationOperationResponse>true</ > PublishLocationOperationResponse> > </GeoLocationConfiguration> > > ​With the new feature developments; In latest IoT Server(master branch); > now we also allow publishing device-info responses through the same > configuration. > > <OperationAnalyticsConfiguration> > <isEnabled>true</isEnabled> > <PublishOperationResponse>true</PublishOperationResponse> > </OperationAnalyticsConfiguration> > > However; there might be use cases for enabling *geo location services* > *without* > *publishing all the device-info* into IoT-Analytics server. Hence, As per > the discussion with Charitha; I am planning to change the above > configuration as below; > > <OperationAnalyticsConfiguration> > <PublishLocationResponse>true</PublishLocationResponse> > <PublishOperationResponse>true</PublishOperationResponse> > </OperationAnalyticsConfiguration> > > WDYT? Appreciate your comments and ideas. > > Best Regards, > ~Rasika > > -- > With Regards, > > *Rasika Perera* > Senior Software Engineer > LinkedIn: http://lk.linkedin.com/in/rasika90 > > <http://wso2.com/signature> > > WSO2 Inc. www.wso2.com > lean.enterprise.middleware > -- Inosh Perera Senior Software Engineer, WSO2 Inc. Tel: 077813 7285, 0785293686
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
