Hello John, We are still slowly migrating our receipt processing to ruote and we hit the following roadblock :
We have a master process, launched by an API call from the user Right after that call, the user uploads one or more pictures asynchronously. Each picture is processed independently. After each picture is processed, the master process should resume I was looking at the way you implemented AlertParticipant in ruote-amqp but I don't think it works for our use case : - The pictures could finish uploading in two month, if the user closes our app and does not reopen it right away, or in the worst case never, if the user never reopens the app, so we can't have each AlertParticipant polling a queue until uploaded - If the user is on a fast connection, the upload could finish before our backend has had time to launch the master process, so we need a way to cache the notifications until they are ready to be processed. The issue here is that the subprocess is not launched by ruote so there is no workitem to store and receive once the upload is done (especially since the reply could happen before any workitem exists) How would you go about implementing something like that ? Regards, Adrien -- -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
