Hi Guys, Sorry.. I don't think that we need to fix this in UI publisher level.. In CEP perspective, what we already have is the correct approach.. IMO, we are trying to solve this issue in a wrong place (which is UI publisher)..
Had a offline chat with Tharik on this, he is suggested that we can implement a hybrid provider where we can get initial information from DB then after sometime in realtime.. This seems like the correct approach for me.. Thanks, Mohan On Thu, Jul 7, 2016 at 8:39 AM, Tharik Kanaka <[email protected]> wrote: > Hi Suho, > > +1 for implementing in UI publisher level. We can send the cached events > as a bulk once a web socket client get subscribed to the UI publisher. Then > push real time events as before. > > This caching should be an optional feature where user could enable when > creating UI publisher. Also we could let user to configure number of cached > records to define limits if required. > > Regards, > > On Thu, Jul 7, 2016 at 1:39 AM, Sriskandarajah Suhothayan <[email protected]> > wrote: > >> This is a valid case, I believe this can be added to the UI publisher. >> @Thilini can you implement caching at UI publisher such that it when a >> gadget connects during the connection time the gadget will get all the >> cached events, and then update itself like how it does now ? >> >> For the proper fix is, events should be pushed to a persistent store via >> DAS and the gadgets should be written to fetch the data from the store >> during startup and then update itself via real-time events. >> >> We have plans to implement this in the next release on top of DAS. >> >> Regards >> Suho >> >> >> >> On Wed, Jul 6, 2016 at 11:19 PM, Sachith Withana <[email protected]> >> wrote: >> >>> Agreed Sinthuja. >>> >>> But what about for a smaller window size (5/10/15 mins)? >>> >>> The reason why I bought up this issue is, in my case, I use several real >>> time gadgets. >>> And at the startup, they are all empty for that user until the data gets >>> pushed in. >>> >>> As an end user, I would like to see the last status of the real time >>> analytics when I log in. >>> >>> Thanks, >>> Sachith >>> >>> On Wed, Jul 6, 2016 at 12:09 PM, Sinthuja Ragendran <[email protected]> >>> wrote: >>> >>>> Hi Sachith, >>>> >>>> If the use-case is to display the 1 hour analytics data from CEP, then >>>> IMO the he/she need to simply store the CEP results into a persistence >>>> store (DAS or RDBMS via RDBMS event publisher), and then let the gadget >>>> read from the persistence store. I don't think caching is a good option in >>>> such cases because anyhow if the server crashes due to some reason the data >>>> is not going to be shown. >>>> >>>> Thanks, >>>> Sinthuja. >>>> >>>> On Wed, Jul 6, 2016 at 10:12 PM, Sachith Withana <[email protected]> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> In the dashboard, the real time data is only shown if the user is >>>>> logged into the dashboard at the time of the data is being pushed. >>>>> >>>>> If the data is being pushed every hour, a new user who logs in would >>>>> potentially have to wait up to one hour to see the real time data, and if >>>>> the user refreshes, then has to wait another hour to see the data, and >>>>> would loose the current data completely. >>>>> >>>>> I understand from the CEP perspective it's similar to fire and forget, >>>>> but can't we add some level of caching to prevent this? >>>>> >>>>> Regards, >>>>> Sachith >>>>> -- >>>>> Sachith Withana >>>>> Software Engineer; WSO2 Inc.; http://wso2.com >>>>> E-mail: sachith AT wso2.com >>>>> M: +94715518127 >>>>> Linked-In: <http://goog_416592669> >>>>> https://lk.linkedin.com/in/sachithwithana >>>>> >>>> >>>> >>>> >>>> -- >>>> *Sinthuja Rajendran* >>>> Technical Lead >>>> WSO2, Inc.:http://wso2.com >>>> >>>> Blog: http://sinthu-rajan.blogspot.com/ >>>> Mobile: +94774273955 >>>> >>>> >>>> >>> >>> >>> -- >>> Sachith Withana >>> Software Engineer; WSO2 Inc.; http://wso2.com >>> E-mail: sachith AT wso2.com >>> M: +94715518127 >>> Linked-In: <http://goog_416592669> >>> https://lk.linkedin.com/in/sachithwithana >>> >> >> >> >> -- >> >> *S. Suhothayan* >> Technical Lead & Team Lead of WSO2 Complex Event Processor >> *WSO2 Inc. *http://wso2.com >> * <http://wso2.com/>* >> lean . enterprise . middleware >> >> >> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: >> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>* >> > > > > -- > > *Tharik Kanaka* > > WSO2, Inc |#20, Palm Grove, Colombo 03, Sri Lanka > > Email: [email protected] | Web: www.wso2.com > -- *V. Mohanadarshan* *Associate Tech Lead,* *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
