Hi, Currently in the mail threads event flow rate, memory consumption, queue size are mentioned as the requirements which need visualizations. What are the additional visualizations needed, could you be more specific on the requirements.?? I would be grateful if you could help me as I am in the final stage of completing my proposal .
Thanks. On Wed, Mar 25, 2015 at 10:34 AM, Sabra Ossen <sa...@wso2.com> wrote: > Hi Mohan, > > Thanks for the clarification. > > Regards. > > On Wed, Mar 25, 2015 at 8:19 AM, Mohanadarshan Vivekanandalingam < > mo...@wso2.com> wrote: > >> >> >> On Mon, Mar 23, 2015 at 2:33 PM, Sabra Ossen <sabra...@gmail.com> wrote: >> >>> Hi, >>> >>> Sorry, I created this new thread since I needed to use my private email >>> address to communicate. >>> >>> So basically so far your idea is to create a Jaggery app for the >>> interface and use the admin service to get data that needs to be shown.?? >>> >> >> Sorry Sabra for the delay.. No need a Jaggary App.. You need to develop a >> carbon UI component for this and use stubs to talk with admin services. >> >> Thanks, >> Mohan >> >> >>> Regards. >>> Sabra. >>> >>> On Sun, Mar 22, 2015 at 1:07 PM, Mohanadarshan Vivekanandalingam < >>> mo...@wso2.com> wrote: >>> >>>> >>>> >>>> On Tue, Mar 17, 2015 at 3:02 PM, Sabra Ossen <sabra...@gmail.com> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> >>>> Sorry Sabra, missed this mail.. >>>> >>>> >>>>> I am Sabra Ossen, an undergraduate of Department of Computer Science >>>>> and Engineering, University of Moratuwa. Currently I am an intern in WSO2. >>>>> >>>>> I am interested in proposal [1] in the GSoC project proposals list. I >>>>> did my fast track training project with WSO2 CEP regarding UI support for >>>>> Siddhi Queries. Therefore I am already familiar with WSO2 CEP and Siddhi >>>>> Queries. >>>>> >>>>> I participated in the hangout and checked the mails in dev regarding >>>>> the Siddhi Process monitor gsoc project. >>>>> >>>>> I have a question regarding the implementation of the api. >>>>> >>>>> - Based on my understanding the api exposes the back end features, >>>>> so would a back end admin service be needed to expose the api. If so >>>>> would >>>>> I have to use the CEP as the server to deploy the web service. >>>>> >>>>> Actually, we need to get process information from Siddhi. Then we need >>>> to create some api for Siddhi engine (currently, we don't have anything >>>> like that). Then we can create an admin service that provide mediation >>>> between the UI and siddhi API. If you have any other interesting idea then >>>> we can discuss about that as well.. >>>> >>>> P.S : For the moment let's stick to single mail thread.. >>>> >>>> Thanks, >>>> Mohan >>>> >>>> >>>> >>>>> Any clarification on the api is appreciated. >>>>> >>>>> Thanks. >>>>> Sabra. >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> *V. Mohanadarshan* >>>> *Software Engineer,* >>>> *Data Technologies Team,* >>>> *WSO2, Inc. http://wso2.com <http://wso2.com> * >>>> *lean.enterprise.middleware.* >>>> >>>> email: mo...@wso2.com >>>> phone:(+94) 771117673 >>>> >>> >>> >> >> >> -- >> *V. Mohanadarshan* >> *Software Engineer,* >> *Data Technologies Team,* >> *WSO2, Inc. http://wso2.com <http://wso2.com> * >> *lean.enterprise.middleware.* >> >> email: mo...@wso2.com >> phone:(+94) 771117673 >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Sabra Ossen > *Software Engineering Intern* > Mobile : +94 (0) 775 837 356 > sa...@wso2.com >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
