These changes look good. Might I suggest another improvement, since we are looking at the function code.
Currently we execute the function code in the same thread as the request which has submitted the function to server. Customer have some times reached out with issues where we see issues when the function code is stuck and causes the distributed system to have issues. It might be a better design to have a concurrent function execution in its own thread pool per server which can be monitored. We can have a Java Future and Executor type behavior in that case. My $0.02. Cheers, *Pulkit Chandra* On Wed, Dec 16, 2015 at 12:27 PM, Dan Smith <[email protected]> wrote: > Hi all, > > Ashvin, Gester and I have gone over our function execution API, and we have > some proposals for how we should improve the function service API to make > it a little bit easier to use. Please take a look at the proposals on the > wiki and let us know what you think: > > > https://cwiki.apache.org/confluence/display/GEODE/Function+Service+Usability+Improvments > > -Dan >
