messaging

I am seeking Python 2.7 alternatives to ZeroMQ that are released under the BSD or MIT license. I am looking for something that supports request-reply and pub-sub messaging patterns. I can serialize the data myself if necessary. I found Twisted from Twisted Matrix Labs but it appears to require a blocking event loop, i.e. reactor.run(). I need a library that will run in the background and let my application check messages upon certain events. Are there any other alternatives? Give nanomsg , a ZeroMQ younger sister, a try - same father, same beauty Yes, it is licensed under MIT /X11 license. Yes

Design Question – Polymorphic Event Handling I’m currently trying to reduce the number of Event Handles in my current project. We have multiple systems that send data over USB. I currently have a routine to read in the messages and parse the initial header details to determine which system the message came from. The headers are a little different, so the EventArgs I created are not the same. Then I notify all “observers” of the change. So what I have right now is the following: public enum Sub1Enums : byte { ID1 = 0x01, ID2 = 0x02 } public enum Sub2Enums : ushort { ID1 = 0xFFFE, ID2 = 0xFFFF }

We have one MQ Queue which receives messages from an external system out of our control. Our system processing the incoming messages is a critical one and needs to be up and running 27x7 no matter what. The order in which the incoming messages are processed is also not negotiable which means we need to process them in exactly the order they arrived. To make sure our system is 100% available we deployed our system to a bunch of physical machines able to process those messages. Once the messages reached our system we put in place a mechanism to make sure the messages processing does not go out

I have some very simple code to do with handlers: Handler seconds=new Handler() { @Override public void handleMessage(Message msg) { bar.incrementProgressBy(5); tView1.setText("r:"+msg); } }; And my thread: Thread seconds_thread=new Thread(new Runnable() { public void run() { try { for (int i=0;i<20 && isRunning.get();i++) { Thread.sleep(1000); Message m = new Message(); Bundle b = new Bundle(); b.putInt("what", 5); // for example m.setData(b); seconds.sendMessage(m); } } catch (Throwable t) { // just end the background thread } } }); As you can see above i am trying to change the value of "

Say you have a JMS queue, and multiple consumers are watching the queue for messages. You want one of the consumers to get all of a particular type of message, so you decide to employ message selectors. For example, you define a property to go in your JMS message header named, targetConsumer . Your message selector, which you apply to the consumer known as, A , is something like WHERE targetConsumer = 'CONSUMER_A' . It's clear that consumer A will now just grab messages with the property set like it is in in the example. Will the other consumers have awareness of that, though? IOW, will

currently I am evaluating different Messaging Systems. There is a question related to Apache Kafka which I could not answer myself. Is it possible for a Kafka producer to create topics and partitions (on existing topics aswell) dynamically? If yes, is there any disadvantage that comes with it? Thanks in Advance Updated: The kafka broker has a property: auto.create.topics.enable If you set that to true if the producer publishes a message to the topic with the new topic name it will automatically create a topic for you. The Confluent Team recommends not doing this because the explosion of topics

Closed . This question needs to be more focused. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it focuses on one problem only by editing this post . Closed 4 years ago . Can someone provide some rules of thumb regarding when to use Message Queueing and what practical real-world problems they are supposed to address? Thanks Asynchronous messaging allows systems to communicate in a disconnected manner. It is not necessary for both systems to be available simultaneously for work to get done. There are other benefits as well. Often