On Mon, May 30, 2016 at 10:49 PM, Imesh Gunaratne <[email protected]> wrote:
> Hi Yashothara, > > On Mon, May 30, 2016 at 2:08 PM, Yashothara Shanmugarajah < > [email protected]> wrote: >> >> >> But now my task is add two parameters time and length *<event> unique >> (<string>attribute, length) and **<event> unique (<string>attribute, >> time). *So the output should be the unique events within the given time >> window or length window according to the unique attribute value. So there >> should be two classes extending WindowProcessor. >> > > Can't we add these attributes to the existing Unique window processor [1] > (as optional) without implementing a new window processor? > [1] https://docs.wso2.com/display/CEP310/Windows#Windows-UniqueWindow > > Yes, your point is valid Imesh.. But IMHO, it is better to have separate implementations.. Technically, all these window types can be implemented as one window. But, I prefer to avoid it due to below reasons.. - To keep the source code simple and more specific for the requirement - We are more concerned about performance and need to avoid unnecessary condition checks and unrelated processing.. Per event latency and TPS are very important benchmarks in CEP. P.S: Anyway, if final implementations are very much identical (and no much validations required) then we can merge them in to one.. Thanks, Mohan > Thanks > > -- > *Imesh Gunaratne* > Software Architect > WSO2 Inc: http://wso2.com > T: +94 11 214 5345 M: +94 77 374 2057 > W: https://medium.com/@imesh TW: @imesh > Lean . Enterprise . Middleware > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *V. Mohanadarshan* *Senior Software Engineer,* *Data Technologies Team,* *WSO2, Inc. http://wso2.com <http://wso2.com> * *lean.enterprise.middleware.* email: [email protected] phone:(+94) 771117673
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
