I believe the 2nd approach will be clear because from the URL itself we know to which topic/service we are sending the event. And this is also the approach used in the old WS-Eventing approach as well.
Suho On Thu, Jan 16, 2014 at 8:09 PM, 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 > > -- *S. Suhothayan* Associate Technical Lead, *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>*
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
