When using REST the subscriber can loose connection or disconnect all together. It would be nice to have a subscription timeout so the broker is not left holding the messages indefinitely for the subscriber. Or is there such an option already?
Currently I created what seems to be a complex solution. Each client application creates a unique queue name and posts that name into a queue named "subscriberqueue" before trying to fetch data from that queue. The producer thats running on the server is a listener to "subscriberqueue" picks up the queue names and saves the to an internal list. The producer then places a copy of the data its holding into each queue that it picked up form the "subscriberqueue" rinse and repeat. If for whatever reason the client application stops their queue name would no longer be pushed onto "subscriberqueue" list and the producer would no longer push data into its queue. It seems like a repoduced most of the functionality of a Topic and I would use one if I knew a subscriber could be assigned a lifespan. Thanks.. -- View this message in context: http://activemq.2283324.n4.nabble.com/Suggestion-for-a-TOPIC-subscriber-REST-API-tp2719846p2719846.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
