In thrift there is a 'oneway' or 'async' or 'fire and forget' call type. I cant recommend those kinds of approaches, since once your system runs into problems you have no feedback. So if you are asking for a one shot, no reply "assume it worked" call, we don't have one (nor would I wish that hell on anyone).
So it boils down to your application architecture. I'm sure you can figure out how to get notifications via callbacks (with background threads or threadpools). Or did you mean something else? -ryan On Wed, Feb 23, 2011 at 2:31 PM, Vishal Kapoor <vishal.kapoor...@gmail.com> wrote: > I have two tables called LIVE and MASTER. > LIVE reports about the MASTER activity and I need to process records in LIVE > almost real time( some business logic) > > if I need to store the activity of entities reported by LIVE rows in MASTER > say in ACTIVITY:LAST_REPORTED > > I could process my data in LIVE and at the same time update the MASTER's > "LIVE REPORTED" attribute with value of current timestamp. > but I was wondering if I can update the MASTER table in a async call so that > I don't compromise on the speed. > was wondering if anyone tried to achieve this or even if it is advisable... > > > thanks, > Vishal Kapoor >
