JPPF Issue Tracker
Please log in to bookmark issues
CLOSED  Task JPPF-584  -  Refactor the distributed class loader into the asynchronous Nio communication model
Posted Mar 30, 2019 - updated Apr 12, 2019
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
  • Status
  • Assigned to
  • Progress
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
  • Resolution
  • Priority
  • Targetted for
    icon_milestones.png JPPF 6.2
Issue description
This is about refactoring the distributed class loader communication model into the more efficient and scalable model introduced in JPPF 6.1 (see Feature request JPPF-549 - Asynchonous communication between server and client and Feature request JPPF-564 - Asynchronous communication betwen node and driver). This includes both driver/node and driver/client communication channels.

These are the last components to switch to the new model. Once it is done, we expect a number of benefits:
  • we will be able to get rid of the old nio code, which should reduce the maintenance burden
  • this should also increase the performance, simply because we will remove parts of the code inherited from the old model, which are still present but not used in the new model
  • increased performance and scalability, because the new nio model is more efficient