Hi Mifan, Thank you for the suggestion, I will talk with the team about the new approach.
Regards, Damith. On Tue, Nov 18, 2014 at 4:42 PM, Mifan Careem <[email protected]> wrote: > Hi Damith (resending to list) > > As discussed, I think a more generic approach which is scalable is as > follows: > > > - User creates an object. An object here is any spatial object (point, > line, polygon) > - User attaches a function or a set of functions to an object. Each > function would have its own set of parameters. > - Based on the full combination, a single execution plan is created > per object (of course, this would have to be optimized as well) > > > So for example, I create a Geo-fence, and then attach within, stationary > and approaches functions to it. This means we will have to restructure some > of the work we did previously but I think that would be the better longer > term approach. > > We will have a register of functions. When a function is added/implemented > to CEP (based on the Geotools version) it will show up in the menu as well > as the function drop down. > > Mifan > > -- > *Mifan Careem* > Director - Solution Architecture, WSO2 Inc. > Member, Sahana Software Foundation > Consultant Spatial Architect > M: +94 773 437 283 > LinkedIn: http://lk.linkedin.com/in/mifan > Skype: mifan_skype > -- Software Engineer WSO2 Inc.; http://wso2.com <http://www.google.com/url?q=http%3A%2F%2Fwso2.com&sa=D&sntz=1&usg=AFQjCNEZvyc0uMD1HhBaEGCBxs6e9fBObg> lean.enterprise.middleware mobile: *+94728671315*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
