Hi All, I think the way this currently works is, if we have a worker manager setup and create an inbound it'll be subscribe from all the members.
But generally with inbound expected functionality should be either work on all workers or one worker at a time. This works fine with polling since it's running on top of NTask. But in the case of MQTT it'll be waiting and listening. I think we need to get this functionality to inbound MQTT as well? WDYT? Interval is not relevant to this inbound and needs to be removed from inbound. Best Regards, Malaka On Fri, Jul 3, 2015 at 11:08 AM, Elilmatha Sivanesan <[email protected]> wrote: > Hi all, > > We are having the common properties interval,coordination and sequence in > the Inbound protocol. There are use cases > > coordination - true (runs only on one worker node) > coordination - false (runs on all worker nodes) > > But in MQTT this use case would not be valid, Where once a node > (consumer) subscribed to a particular topic will consume the message. > > Any thoughts on this. > > Thanks, > -- > *S.Elilmatha* > Associate Software Engineer, > > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > Mobile 0779842221. > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Best Regards, Malaka Silva Senior Tech Lead M: +94 777 219 791 Tel : 94 11 214 5345 Fax :94 11 2145300 Skype : malaka.sampath.silva LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77 Blog : http://mrmalakasilva.blogspot.com/ WSO2, Inc. lean . enterprise . middleware http://www.wso2.com/ http://www.wso2.com/about/team/malaka-silva/ <http://wso2.com/about/team/malaka-silva/> Save a tree -Conserve nature & Save the world for your future. Print this email only if it is absolutely necessary.
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
