Configure retry/consume parameters on consumer side about redis-smq HOT 4 CLOSED

Also more than happy to submit a PR for whichever solution we're happy with.

from redis-smq.

@TiddoLangerak Thank you for opening this issue.

As far as I understand, consuming parameters can only be configured on the producer side.

I want to clarify that is not the case. The Producer does not handle or accept in anyway consuming parameters. It does not even know about their existence. Properties like (consumeTimeout, retryDelay, ttl, retryThreshold) are called "Consuming parameters" and are message properties. They can not be configured neither on the Producer side nor on the Consumer side.

These properties can be set at the Message level for a given Message instance and are handled by RedisSMQ at the Consumer side. By the way, the link you provided points out to Message API reference.

from redis-smq.

I'm sorry if I didn't explain myself properly. With "Consumer side" and "Producer side" I mean the nodes (workers/clients/applications), not the redis-smq classes.

I.e. this is the situation:

The Producer Node creates a message and calls a producer instance to send it.
The Consumer Node consumes the message using a consumer instance.

Since the Producer Node creates the message, it is also in full control over the retry/timeout parameters, and therefore controls resources of the Consumer Node.

As far as I can tell, there's no way for the Consumer Node to control retry/timeout behaviour, as the message is created by the Producer Node, and there's no mechanism for the Consumer Node to set/override these parameters. Hence, my proposals.

I hope that this clears it up?

from redis-smq.

Hi @weyoss - could you please still consider the above?

from redis-smq.