Hi Mohan, You may try to reuse the non-blocking transport implementation[1] (based on ESB PTT architecture) done on top of HTTPCore NIO. It doesn't have any direct relationship between Siddhi as its a generic non-blocking transport implementation.
[1] https://github.com/kasun04/siddhi-esb/tree/master/modules/transports On Fri, Jan 17, 2014 at 2:00 PM, Paul Fremantle <p...@wso2.com> wrote: > How does this relate to the work that Kasun did with his non-blocking HTTP > input adapter for CEP? > > Paul > > > On 16 January 2014 14:39, Mohanadarshan Vivekanandalingam > <mo...@wso2.com>wrote: > >> Hi All, >> >> We have started working on implementing HTTP input event adaptor for CEP. >> Using this adaptor, we can send any type of message (No need to be a >> defined format) to CEP for processing. >> HTTP event adaptor will have the ability to forward the incoming messages >> to a topic, based on the user configuration. Here, we can follow two >> approaches on developing the adaptor. We are looking >> for a best option based on below, >> >> 1) We can have a single http endpoint (eg : >> *https://localhost:9443/message_endpoint >> <https://localhost:9443/message_endpoint>*) and all the users can send >> events to this specific endpoint. Here user need to set a custom header >> which specifying the corresponding topic where events needs to be forwarded. >> >> 2) We can create dynamic endpoints based on the configuration given by >> the user. For example if the topic is stockQuote then event adaptor can >> register a dynamic endpoint like *https://localhost:9443/endpoint/stockQuote >> <https://localhost:9443/endpoint/stockQuote> *. then users can send >> events to corresponding dynamic endpoint. >> >> What would be the best option that we can follow on [1] & [2]. Appreciate >> your ideas.. >> >> Thanks & Regards, >> Mohan >> >> >> -- >> *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 >> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Paul Fremantle > CTO and Co-Founder, WSO2 > OASIS WS-RX TC Co-chair, Apache Member > > UK: +44 207 096 0336 > US: +1 646 595 7614 > > blog: http://pzf.fremantle.org > twitter.com/pzfreo > p...@wso2.com > > wso2.com Lean Enterprise Middleware > > Disclaimer: This communication may contain privileged or other > confidential information and is intended exclusively for the addressee/s. > If you are not the intended recipient/s, or believe that you may have > received this communication in error, please reply to the sender indicating > that fact and delete the copy you received and in addition, you should not > print, copy, retransmit, disseminate, or otherwise use the information > contained in this communication. Internet communications cannot be > guaranteed to be timely, secure, error or virus-free. The sender does not > accept liability for any errors or omissions. > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
