persistence - Mule: after delivering a message, save the current timestamp for later use. What's the correct idiom? -


i'm connecting third-party web service retrieve rows underlying database. can optionally pass parameter this:

http://server.com/resource?createdafter=[yyyy-mm-dd hh:ss] 

to rows created after given date.

this means have store current timestamp (using #[function:datestamp:...], no problem) in 1 message scope , retrieve in another.

it implies timestamp should preserved in case of outage.

obviously, use subflow containing file endpoint, saving in designated file on path. but, intuitively, based on (very!) limited experience, feels hackish.

what's correct idiom solve this?

thanks!

the object store module designed that: allow save bits of information flows.

see:


Comments

Popular posts from this blog

jquery - How can I dynamically add a browser tab? -

node.js - Getting the socket id,user id pair of a logged in user(s) -

keyboard - C++ GetAsyncKeyState alternative -