Complex use case - Interleaved splitter with countdown timer

[Mark Fisher]

I might be missing something entirely, but I thought I would throw out one more idea:

event-source -> queue-channel <- poller -> output-channel

Of course, since you apparently have multiple event sources (A, B, C in the examples), this could involve multiple queue-channel/poller pairs and a router between the event-source and those queue-channels.

Does this make any sense at all for the use case?

-Mark

[iwein]

Thanks again for sharing, I'm looking forward to the blog.

Also an interesting question to ponder is if spring integration should natively support a heartbeat mechanism or is it sufficient to just natively support a delay channel and let the user implement whatever heartbeat mechanism they need. I think it is very difficult to generalise on heartbeat use cases but would be interested to hear your opinion on this.

Support for a DelayQueue is a good first step. I think we'll have to wait a bit to see different things like yours come up in the wild before choosing an approach in the framework (if any). Of course it doesn't hurt to create an issue for it once you have your version done, it might turn out to be a very good option

[rock_star]

Hi Guys,

was there any further update on this? Sorry to activate the old thread. But I think I will be working on similar to this.

I have a scenario like --

Let us say I have messages coming on queue Tib/IBM queue with priorties ( in bracket) A(1), B(1), C(2), D(3).
Lets say A(1) are 100 messages , C(2) 10 messages, D(3) 5 messages.

I can take them and put them on priorty-channel

I want to pass on the all A(1)( highest priority messages) to next queue after processing. But before taking C(2) type of messages from priority-channel
I want to have some delay because there could be a case that some client process can put A(1) type of messages. Same while taking D(3) kind of messages.

Any idea , is there is any thing SI of help or I can sutomize?