In the last post of the Executor Framework blog post series, I had written about executing a single task from a collection of tasks, creating a Callable task from a Runnable task, cached Thread Pool and
In the Part II of Executor Framework blog post series, I had written about creating cancellable
Runnable task and creating
Runnable task with a timeout with the help of this framework. I had also written about two
submit methods of
ExecutorService, which are used to create asynchronous task.
In the Part I of Executor Framework blog post series, I had written how it can be used to create a single worker thread for sequential execution of tasks and create a thread pool of fixed number of threads. In this blog post, I’m writing about the following uses of Executor framework:
We know you enjoy reading digital business and technology blogs. Well, that's why you are here. Isn't it? We share this love as well. That's why we created a place where our digital professionals from different technology and business teams could come and discuss ideas to foster business transformation through technology, digital philosophy and user centric design.
The views and opinions expressed in this weblog represent that of the author and not those of the employer. e-Zest holds no responsibility for the correctness of it.
e-Zest Solutions is digital experience engineering company with facilities in the United States (Detroit & San Jose), Germany (Hannover), United Kingdom (London UK) and India (Pune) with global clientele. Our services include custom software development, offshore software development, UX consulting, BigData, Managed cloud Services (Azure & AWS), SharePoint consulting/Migration, Enterprise Java application development, Automated software testing services.