any update one this? Whats the approach we are taking now
On Mon, Jul 6, 2015 at 4:34 PM, Tharindu Munasinghe < [email protected]> wrote: > Yes , exactly they are not scalable models. There are several > implementations I found but many of them doesn't > provide context-sensitiveness for custom languages. As I can see the > scalability can be achieved only if the auto completion logic resides > within Antlr4 context right? . > > I have started a discussion in antlr-discussion google group regarding > this matter. I am still looking for an alternative but haven't come across > a scalable solution. Meanwhile if you have an alternative in mind, please > let me know. > > > *Th**a**rindu Munasin**ghe.* > *Undergraduate ,Department of Computer **S**cience and Engineering* > *University of Moratuwa.* > *Contact no. +94770460887 <%2B94770460887>* > > > > > On Sun, Jul 5, 2015 at 9:38 PM, Sriskandarajah Suhothayan <[email protected]> > wrote: > >> The both model you are progressing are not scalable, and error prone. If >> we make any change to the grammar then we have to also fix that in several >> places. >> >> Isn't there any other alternatives? >> >> Suho >> >> On Tue, Jun 30, 2015 at 4:59 AM, Tharindu Munasinghe < >> [email protected]> wrote: >> >>> Hi Mentors, >>> >>> I have been working on the context-aware auto completion feature. There >>> is a function called getExpectedTokensInCurrentRule() in Antlr4 API >>> which returns the possible next tokens based on the current rule context. I >>> have tried to use that function to get the possible tokens, but as I can >>> see this function will only work with valid input that can be parsed >>> without errors. While the query is incomplete (while user is typing the >>> query) it will only generate a generic error without returning any parsing >>> information. >>> >>> I have two alternatives in mind to overcome the issue . >>> 1. create set of regular expressions to match the last input token and >>> present a set of predefined suggestion lists. >>> 2. create token graph similar to following diagram and suggest the >>> children of the current token >>> >>> >>> >>> >>> I would be grateful if you can provide feedback regarding which method >>> to implement. Any alternative suggestions are highly appreciated. >>> >>> >>> On 15 June 2015 at 09:36, Tharindu Munasinghe <[email protected] >>> > wrote: >>> >>>> Hi Mentors, >>>> >>>> I have almost completed the implementation of syntax and semantic error >>>> highlighting mechanism. Now the errors are listed in appropriate >>>> lines while user is writing the query . Number of server calls are reduced >>>> significantly , but still more optimizations can be done on this. >>>> >>>> This week I will be working on the auto completion feature , current >>>> editor does have all-text auto completion. But I am trying to reduce the >>>> suggestion list based on the context-awareness. >>>> >>>> Can we have a meeting in this week to verify the work I have already >>>> done and to discuss the proceedings of this project ?. >>>> >>>> On 11 June 2015 at 08:08, Tharindu Munasinghe < >>>> [email protected]> wrote: >>>> >>>>> Hi Suho, >>>>> >>>>> >>>>> *Weekly Progress Update* >>>>> >>>>> I have been working on syntax and semantic error highlighting >>>>> mechanism. Client side syntax checking is almost completed and I managed >>>>> to >>>>> integrate new editor with CEP 4.0 .Once there are no syntax errors , the >>>>> query will be submitted to the server side Siddhi compiler for semantic >>>>> error checking . >>>>> >>>>> Since the syntax errors are checked in client side, only the semantic >>>>> error messages will be getting from the server . But there was an issue in >>>>> displaying the error messages since some of the semantic error messages do >>>>> not contain the line numbers. >>>>> >>>>> To overcome the issue , I divided the query into top level parser >>>>> rules ( define_stream, execution_element, ...) and send the code to the >>>>> server in a constructive manner . So that the line which raise the error >>>>> message can be identified. >>>>> >>>>> suppose the code is similar to this, >>>>> >>>>> 1. define stream foo(a int ,b string); //define_stream : at line >>>>> 1--> A >>>>> 2. >>>>> 3. define stream foo(a int ,b int); //define_stream : at line 3 >>>>> --->B >>>>> 4. >>>>> 5. from foo //execution_element : at line >>>>> 5----> C >>>>> 6. select a >>>>> 7. insert into bar; >>>>> >>>>> >>>>> If the code has no syntax errors then,it will be submitted to >>>>> server as follows, >>>>> A , A+B , A+B+C >>>>> >>>>> Since this feature can't be demonstrated in github pages. It would >>>>> be great if we can meet and verify the progress before sending the PR. >>>>> >>>>> Thanks >>>>> >>>>> On 3 June 2015 at 16:06, Sriskandarajah Suhothayan <[email protected]> >>>>> wrote: >>>>> >>>>>> Thanks for the update, yes keep us posted >>>>>> >>>>>> Suho >>>>>> >>>>>> On Wed, Jun 3, 2015 at 9:26 AM, Tharindu Munasinghe < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi Suho >>>>>>> >>>>>>> I am working on the client side syntax checker (improving the error >>>>>>> messages) and integrating the new editor with CEP. As soon as I >>>>>>> complete them I will review the work with you before sending PRs . >>>>>>> Sorry for delay in updating the progress. I will update you >>>>>>> frequently >>>>>>> from now onward. >>>>>>> >>>>>>> Thanks, >>>>>>> >>>>>>> On 2 June 2015 at 21:06, Sriskandarajah Suhothayan <[email protected]> >>>>>>> wrote: >>>>>>> > Hi Tharindu >>>>>>> > >>>>>>> > Your work looks good, do you have any updates ? >>>>>>> > >>>>>>> > Suho >>>>>>> > >>>>>>> > On Sun, May 24, 2015 at 9:54 AM, Mohanadarshan Vivekanandalingam >>>>>>> > <[email protected]> wrote: >>>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>>> >> On Wed, May 20, 2015 at 2:27 AM, Tharindu Munasinghe >>>>>>> >> <[email protected]> wrote: >>>>>>> >>> >>>>>>> >>> Hi Mentors, >>>>>>> >> >>>>>>> >> >>>>>>> >> Hi Tharindu, >>>>>>> >> >>>>>>> >>> >>>>>>> >>> >>>>>>> >>> I have started the initial implementation of client-side >>>>>>> features like >>>>>>> >>> syntax highlighting , code completion and code-snippets. I have >>>>>>> tried both >>>>>>> >>> ACE editor as well as Code-mirror libraries but according to my >>>>>>> observation, >>>>>>> >>> ACE editor can easily be customized for domain specific >>>>>>> languages. >>>>>>> >>> >>>>>>> >>> Current implementation [1] is based on ACE library. The progress >>>>>>> of the >>>>>>> >>> implementation as follows, >>>>>>> >>> >>>>>>> >>> Syntax Highlighting :almost completed >>>>>>> >>> >>>>>>> >>> Code completion : >>>>>>> >>> Currently the keywords,annotations, and locally defined >>>>>>> >>> identifiers can be suggested.But the suggestion list still need >>>>>>> to be >>>>>>> >>> optimized based on the context awareness. >>>>>>> >>> >>>>>>> >>> Code snippets: >>>>>>> >>> Predefined code snippets are supported for now (Eg: >>>>>>> "defStr": >>>>>>> >>> define stream , "attr","attrS") . User defined code snippets >>>>>>> have to be >>>>>>> >>> handled . >>>>>>> >>> >>>>>>> >>> Error checking: >>>>>>> >>> Client side Siddhi parser (Antlr4 in JS runtime) was >>>>>>> >>> integrated with Siddhi Editor. It just verify the syntactical >>>>>>> correctness of >>>>>>> >>> the query and shows error indicators with error messages on >>>>>>> relevant lines >>>>>>> >>> immediately . Currently the error messages are somewhat abstract >>>>>>> and there >>>>>>> >>> are issues in triggering the event as well . So there are >>>>>>> improvements still >>>>>>> >>> need to be done on this. For now, This feature only focuses on >>>>>>> the syntax >>>>>>> >>> that can be evaluated at client-side. For semantic >>>>>>> verifications, Ajax >>>>>>> >>> requests need to be sent (if only the client side parser doesn't >>>>>>> find any >>>>>>> >>> syntax errors) to the existing server-side Siddhi Compiler (That >>>>>>> part is yet >>>>>>> >>> to be done). >>>>>>> >>> >>>>>>> >>> >>>>>>> >>> The source code at [1] only contains the client side features >>>>>>> listed >>>>>>> >>> above. This project is maintained just for the ease of testing >>>>>>> and debugging >>>>>>> >>> the front end specific features. Once the client-side specific >>>>>>> features are >>>>>>> >>> implemented and tested properly , this could be integrated and >>>>>>> merged with >>>>>>> >>> carbon-event-processing project. Afterwards I will continue to >>>>>>> work on back >>>>>>> >>> end related feature ,and will send PRs based on the improvements >>>>>>> . >>>>>>> >>> >>>>>>> >> >>>>>>> >> First of all, sorry for the delay.. I have tried out the editor, >>>>>>> it is >>>>>>> >> really cool.. I believe GSOC coding is starting by Tomorrow, >>>>>>> great to see >>>>>>> >> that you have started already.. I think, you have done a chat >>>>>>> with Srinath >>>>>>> >> and Suho regarding this and planned accordingly.. >>>>>>> >> >>>>>>> >> FYI, we have done some improvements for our existing editor as >>>>>>> well.. >>>>>>> >> Please check our CEP 4.0.0 alpha pack for more information.. >>>>>>> >> >>>>>>> >> Thanks, >>>>>>> >> Mohan >>>>>>> >> >>>>>>> >> >>>>>>> >>> >>>>>>> >>> Please find demo page for the Siddhi editor is hosted on [2] . >>>>>>> Highly >>>>>>> >>> appreciate your feedbacks and suggestions on this. >>>>>>> >>> >>>>>>> >>> [1]: https://github.com/TharinduMunasinge/CEP-Siddhi_Editor/ >>>>>>> >>> [2]: >>>>>>> http://tharindumunasinge.github.io/CEP-Siddhi_Editor/ace_editor/ >>>>>>> >>> >>>>>>> >>> Thanks! >>>>>>> >>> >>>>>>> >>> On 7 May 2015 at 00:22, Tharindu Munasinghe < >>>>>>> [email protected]> >>>>>>> >>> wrote: >>>>>>> >>>> >>>>>>> >>>> Thanks Srinath! >>>>>>> >>>> >>>>>>> >>>> I had a quick discussion with Suho last week. He gave me the >>>>>>> initial >>>>>>> >>>> work flow and priorities of the features listed in the proposal. >>>>>>> >>>> >>>>>>> >>>> I am currently testing Antr4,Code-mirror and Ace libraries for >>>>>>> the >>>>>>> >>>> implementation purposes. Built the CEP 4.0 and have been getting >>>>>>> >>>> familiar with SiddhiQL 3.0. >>>>>>> >>>> >>>>>>> >>>> Sure we can meet and discuss further details probably on Next >>>>>>> Monday. >>>>>>> >>>> So that I will be able to come up with something thing to demo >>>>>>> the >>>>>>> >>>> progress. Please let me know the time (or else a possible date >>>>>>> in next >>>>>>> >>>> week) for the meeting . >>>>>>> >>>> >>>>>>> >>>> >>>>>>> >>>> Thanks, >>>>>>> >>>> >>>>>>> >>>> On 5 May 2015 at 09:01, Srinath Perera <[email protected]> >>>>>>> wrote: >>>>>>> >>>> > Tharindu, congratulations on the proposal! >>>>>>> >>>> > >>>>>>> >>>> > Shall we meet and discuss sometime this or the following week? >>>>>>> >>>> > >>>>>>> >>>> > On Wed, Apr 29, 2015 at 2:46 PM, Tharindu Munasinghe >>>>>>> >>>> > <[email protected]> wrote: >>>>>>> >>>> >> >>>>>>> >>>> >> Hi Mentors, >>>>>>> >>>> >> >>>>>>> >>>> >> First of all thanks for selecting my proposal on $subject . >>>>>>> I am >>>>>>> >>>> >> planing to complete most of the basic implementations >>>>>>> before the >>>>>>> >>>> >> official Gsoc starting date (May 25) . Before that I would >>>>>>> like to >>>>>>> >>>> >> have a review for the design decisions included in the >>>>>>> proposal. >>>>>>> >>>> >> It would be great if you can review them and provide >>>>>>> feedbacks and >>>>>>> >>>> >> suggestions . >>>>>>> >>>> >> >>>>>>> >>>> >> Thanks, >>>>>>> >>>> >> >>>>>>> >>>> >> On 28 March 2015 at 12:09, Tharindu Munasinghe >>>>>>> >>>> >> <[email protected]> wrote: >>>>>>> >>>> >> > Hi all, >>>>>>> >>>> >> > >>>>>>> >>>> >> > Attached here is the proposal I submitted for $subject . >>>>>>> >>>> >> > >>>>>>> >>>> >> > >>>>>>> >>>> >> > >>>>>>> >>>> >> > >>>>>>> >>>> >> > >>>>>>> https://docs.google.com/a/cse.mrt.ac.lk/document/d/1Txl5uZbLYIX8slLR8F5kI8U0Se79tBgHxw2dA3hMIhI/edit# >>>>>>> >>>> >> > >>>>>>> >>>> >> > On 28 March 2015 at 00:08, Tharindu Munasinghe < >>>>>>> [email protected]> >>>>>>> >>>> >> > wrote: >>>>>>> >>>> >> >> >>>>>>> >>>> >> >> [Adding [email protected]] >>>>>>> >>>> >> >> >>>>>>> >>>> >> >> On Wed, Mar 4, 2015 at 12:41 AM, Tharindu Munasinghe >>>>>>> >>>> >> >> <[email protected]> >>>>>>> >>>> >> >> wrote: >>>>>>> >>>> >> >>> >>>>>>> >>>> >> >>> Hi all, >>>>>>> >>>> >> >>> Thanks Mohan for the quick response. Sure.. >>>>>>> according to >>>>>>> >>>> >> >>> the >>>>>>> >>>> >> >>> currently available slots I have sent a calendar >>>>>>> invitation for >>>>>>> >>>> >> >>> the >>>>>>> >>>> >> >>> discussion on $subject .Please find the invitation at >>>>>>> 3.00 PM >>>>>>> >>>> >> >>> today >>>>>>> >>>> >> >>> and let >>>>>>> >>>> >> >>> me know the availability by then. >>>>>>> >>>> >> >>> >>>>>>> >>>> >> >>> Thanks, >>>>>>> >>>> >> >>> >>>>>>> >>>> >> >>> >>>>>>> >>>> >> >>> On Tue, Mar 3, 2015 at 10:47 PM, Mohanadarshan >>>>>>> Vivekanandalingam >>>>>>> >>>> >> >>> <[email protected]> wrote: >>>>>>> >>>> >> >>>> >>>>>>> >>>> >> >>>> >>>>>>> >>>> >> >>>> >>>>>>> >>>> >> >>>> On Tue, Mar 3, 2015 at 5:19 PM, Tharindu Munasinghe >>>>>>> >>>> >> >>>> <[email protected]> >>>>>>> >>>> >> >>>> wrote: >>>>>>> >>>> >> >>>>> >>>>>>> >>>> >> >>>>> Hi, >>>>>>> >>>> >> >>>>> >>>>>>> >>>> >> >>>> >>>>>>> >>>> >> >>>> Hi Tharindu, >>>>>>> >>>> >> >>>> >>>>>>> >>>> >> >>>>> >>>>>>> >>>> >> >>>>> I am Tharindu Munasinghe , an undergraduate from >>>>>>> Department of >>>>>>> >>>> >> >>>>> Computer Science and Engineering, University of >>>>>>> Moratuwa >>>>>>> >>>> >> >>>>> .Currently >>>>>>> >>>> >> >>>>> I am an >>>>>>> >>>> >> >>>>> intern at WSO2. >>>>>>> >>>> >> >>>>> >>>>>>> >>>> >> >>>>> I went through the GSoC proposal list and interested in >>>>>>> >>>> >> >>>>> proposal [1] >>>>>>> >>>> >> >>>>> and looking forward to contribute . I am already >>>>>>> familiar with >>>>>>> >>>> >> >>>>> WSO2 >>>>>>> >>>> >> >>>>> CEP and >>>>>>> >>>> >> >>>>> Siddhi while working on my fast track training >>>>>>> project. >>>>>>> >>>> >> >>>>> >>>>>>> >>>> >> >>>>> Please let me know if we could have a discussion on >>>>>>> $subject. >>>>>>> >>>> >> >>>>> >>>>>>> >>>> >> >>>> >>>>>>> >>>> >> >>>> Happy to hear that you like to work on $subject.. Sure, >>>>>>> we can >>>>>>> >>>> >> >>>> have >>>>>>> >>>> >> >>>> discussion. Please check for a convenient time with >>>>>>> Suho & >>>>>>> >>>> >> >>>> Srinath.. >>>>>>> >>>> >> >>>> >>>>>>> >>>> >> >>>> Thanks, >>>>>>> >>>> >> >>>> Mohan >>>>>>> >>>> >> >>>> >>>>>>> >>>> >> >>>>> >>>>>>> >>>> >> >>>>> [1] Siddhi Editor for WSO2 CEP >>>>>>> >>>> >> >>>>> >>>>>>> >>>> >> >>>>> -- >>>>>>> >>>> >> >>>>> Tharindu Munasinghe >>>>>>> >>>> >> >>>>> Software Engineering Intern >>>>>>> >>>> >> >>>>> WSO2 Inc.(http://wso2.com) >>>>>>> >>>> >> >>>>> SRI LANKA >>>>>>> >>>> >> >>>>> >>>>>>> >>>> >> >>>>> Mobile: +94 77460887 >>>>>>> >>>> >> >>>>> E-Mail: [email protected] >>>>>>> >>>> >> >>>>> >>>>>>> >>>> >> >>>>> _______________________________________________ >>>>>>> >>>> >> >>>>> Dev mailing list >>>>>>> >>>> >> >>>>> [email protected] >>>>>>> >>>> >> >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>> >> >>>>> >>>>>>> >>>> >> >>>> >>>>>>> >>>> >> >>>> >>>>>>> >>>> >> >>>> >>>>>>> >>>> >> >>>> -- >>>>>>> >>>> >> >>>> V. Mohanadarshan >>>>>>> >>>> >> >>>> Software Engineer, >>>>>>> >>>> >> >>>> Data Technologies Team, >>>>>>> >>>> >> >>>> WSO2, Inc. http://wso2.com >>>>>>> >>>> >> >>>> lean.enterprise.middleware. >>>>>>> >>>> >> >>>> >>>>>>> >>>> >> >>>> email: [email protected] >>>>>>> >>>> >> >>>> phone:(+94) 771117673 >>>>>>> >>>> >> >>> >>>>>>> >>>> >> >>> >>>>>>> >>>> >> >>> >>>>>>> >>>> >> >>> >>>>>>> >>>> >> >>> -- >>>>>>> >>>> >> >>> Tharindu Munasinghe >>>>>>> >>>> >> >>> Software Engineering Intern >>>>>>> >>>> >> >>> WSO2 Inc.(http://wso2.com) >>>>>>> >>>> >> >>> SRI LANKA >>>>>>> >>>> >> >>> >>>>>>> >>>> >> >>> Mobile: +94 77460887 >>>>>>> >>>> >> >>> E-Mail: [email protected] >>>>>>> >>>> >> >> >>>>>>> >>>> >> >> >>>>>>> >>>> >> >> >>>>>>> >>>> >> >> >>>>>>> >>>> >> >> -- >>>>>>> >>>> >> >> Tharindu Munasinghe >>>>>>> >>>> >> >> Software Engineering Intern >>>>>>> >>>> >> >> WSO2 Inc.(http://wso2.com) >>>>>>> >>>> >> >> SRI LANKA >>>>>>> >>>> >> >> >>>>>>> >>>> >> >> Mobile: +94 77460887 >>>>>>> >>>> >> >> E-Mail: [email protected] >>>>>>> >>>> >> > >>>>>>> >>>> >> > >>>>>>> >>>> >> > >>>>>>> >>>> >> > >>>>>>> >>>> >> > -- >>>>>>> >>>> >> > Tharindu Munasinghe. >>>>>>> >>>> >> > Undergraduate ,Department of Computer Science and >>>>>>> Engineering >>>>>>> >>>> >> > University of Moratuwa. >>>>>>> >>>> >> > Contact no. +94770460887 >>>>>>> >>>> >> >>>>>>> >>>> >> >>>>>>> >>>> >> >>>>>>> >>>> >> -- >>>>>>> >>>> >> Tharindu Munasinghe. >>>>>>> >>>> >> Undergraduate ,Department of Computer Science and Engineering >>>>>>> >>>> >> University of Moratuwa. >>>>>>> >>>> >> Contact no. +94770460887 >>>>>>> >>>> > >>>>>>> >>>> > >>>>>>> >>>> > >>>>>>> >>>> > >>>>>>> >>>> > -- >>>>>>> >>>> > ============================ >>>>>>> >>>> > Blog: http://srinathsview.blogspot.com >>>>>>> twitter:@srinath_perera >>>>>>> >>>> > Site: http://people.apache.org/~hemapani/ >>>>>>> >>>> > Photos: http://www.flickr.com/photos/hemapani/ >>>>>>> >>>> > Phone: 0772360902 >>>>>>> >>>> >>>>>>> >>>> >>>>>>> >>>> >>>>>>> >>>> -- >>>>>>> >>>> Tharindu Munasinghe. >>>>>>> >>>> Undergraduate ,Department of Computer Science and Engineering >>>>>>> >>>> University of Moratuwa. >>>>>>> >>>> Contact no. +94770460887 >>>>>>> >>> >>>>>>> >>> >>>>>>> >>> >>>>>>> >>> >>>>>>> >>> -- >>>>>>> >>> Tharindu Munasinghe. >>>>>>> >>> Undergraduate ,Department of Computer Science and Engineering >>>>>>> >>> University of Moratuwa. >>>>>>> >>> Contact no. +94770460887 >>>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>>> >> >>>>>>> >> -- >>>>>>> >> V. Mohanadarshan >>>>>>> >> Senior Software Engineer, >>>>>>> >> Data Technologies Team, >>>>>>> >> WSO2, Inc. http://wso2.com >>>>>>> >> lean.enterprise.middleware. >>>>>>> >> >>>>>>> >> email: [email protected] >>>>>>> >> phone:(+94) 771117673 >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > -- >>>>>>> > S. Suhothayan >>>>>>> > Technical Lead & Team Lead of WSO2 Complex Event Processor >>>>>>> > WSO2 Inc. http://wso2.com >>>>>>> > lean . enterprise . middleware >>>>>>> > >>>>>>> > cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ >>>>>>> > twitter: http://twitter.com/suhothayan | linked-in: >>>>>>> > http://lk.linkedin.com/in/suhothayan >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Tharindu Munasinghe. >>>>>>> Undergraduate ,Department of Computer Science and Engineering >>>>>>> University of Moratuwa. >>>>>>> Contact no. +94770460887 >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> *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>* >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Th**a**rindu Munasin**ghe.* >>>>> *Undergraduate ,Department of Computer **S**cience and Engineering* >>>>> *University of Moratuwa.* >>>>> *Contact no. +94770460887* >>>>> >>>> >>>> >>>> >>>> -- >>>> *Th**a**rindu Munasin**ghe.* >>>> *Undergraduate ,Department of Computer **S**cience and Engineering* >>>> *University of Moratuwa.* >>>> *Contact no. +94770460887* >>>> >>> >>> >>> >>> -- >>> *Th**a**rindu Munasin**ghe.* >>> *Undergraduate ,Department of Computer **S**cience and Engineering* >>> *University of Moratuwa.* >>> *Contact no. +94770460887* >>> >> >> >> >> -- >> >> *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>* >> > > -- *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 | 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>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
