JPPF, java, parallel computing, distributed computing, grid computing, parallel, distributed, cluster, grid, cloud, open source, android, .net

The open source
grid computing

 Home   About   Features   Download   Documentation   On Github   Forums 
June 04, 2023, 09:05:59 AM *
Please login or register.

Login with username, password and session length
Advanced search  
News: New users, please read this message. Thank you!
  Home Help Search Login Register  
Pages: [1]   Go Down

Author Topic: Peer driver communication  (Read 1482 times)


  • JPPF Master
  • ***
  • Posts: 31
Peer driver communication
« on: June 19, 2017, 02:29:36 PM »

With such an architecture; peer to peer connected drivers with only local node and each driver connected to seperate one client (client-driver connection one-to-one), do drivers aware of tasks which delivered by other drivers to the nodes and take this into account while delivering tasks?


  • Administrator
  • JPPF Council Member
  • *****
  • Posts: 2272
    • JPPF Web site
Re: Peer driver communication
« Reply #1 on: June 20, 2017, 06:36:49 AM »


The short answer is yes. If for example, clientA sends a job to driverA, and local nodeA is already busy, driverA then sends the job to driverB which executes it on local nodeB, then the resulting executed tasks will be sent all the way back to clientA. This is true for any level of inderection in the job execution path. In other words, the results of a job are always delivered to the client that submitted it. This is possible because the job always maintains a "uuid path" in the form "clientUuid / driver1Uuid / ... / driverNUuid", so JPPF always knows where the job comes from and where to send the results back.

I hope this clarifies,
Pages: [1]   Go Up
JPPF Powered by SMF 2.0 RC5 | SMF © 2006–2011, Simple Machines LLC Get JPPF at Fast, secure and Free Open Source software downloads