messaging

I have a JMS client which is producing messages and sending over a JMS queue to its unique consumer. What I want is more than one consumer getting those messages. The first thing that comes to my mind is converting the queue to a topic, so current and new consumers can subscribe and get the same message delivered to all of them. This will obviously involve modifying the current clients code in both producer and consumer side of things. I would like to also look at other options like creating a second queue, so that I don't have to modify the existing consumer. I believe there are advantages in

We are in need of a distributed architecture messaging system/service bus with the capability of Publish/Subscribe. Does anyone have any reccomendations for a framework that we can use for .net applications? Dale Ragan NServiceBus is growing in popularity. It is open source as well. Here is a Hanselminutes episode with Scott Hanselman talking with Udi Dahan about NServiceBus to help grok it. You should definitely evaluate using it. UPDATE: There's also a DNR TV episode which shows what it's like to build an NServiceBus solution from scratch here: http://www.dnrtv.com/default.aspx?showNum=199

I have a method that occasionally crashes. -(void)foo{ [self doSomething]; [self.delegate didFinish]; [self doSomethingElse]; } -doSomething works correctly, then I call to a delegate -didFinish. Within -didFinish, the reference to this object might be set to nil, releasing it under ARC. When the method crashes, it does so on -doSomethingElse. My assumption was that self would be strong within a method, allowing the function to complete. Is self weak or strong? Is there documentation on this? What would the reasoning be for it being strong or weak? Edit Upon being inspired by some of the

I have built the following model to handle user's message exchange: create_table "messages", :force => true do |t| t.integer "source_id" t.integer "destination_id" t.string "object" t.string "body" t.datetime "created_at" t.datetime "updated_at" end These are its associations: class Message < ActiveRecord::Base belongs_to :sender, :class_name=>'User', :foreign_key=>'source_id' belongs_to :reciever, :class_name=>'User', :foreign_key=>'destination_id' end And these other are the associations on the other side (the user model): has_many :sent_messages, :class_name=> 'Message', :foreign_key=>