JPPF Issue Tracker
star_faded.png
Please log in to bookmark issues
feature_request_small.png
CLOSED  Feature request JPPF-175  -  Extend the JPPF network protocol to enable properly closing the network connections
Posted Aug 01, 2013 - updated Nov 12, 2013
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Feature request
  • Status
     
    		 Closed
  • Assigned to
    lolo4j
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    lolo4j
  • Owned by
    Not owned by anyone
  • Category
    Networking
  • Resolution
    RESOLVED
  • Priority
    Normal
  • Targetted for
    icon_milestones.png JPPF 4.0
Issue description
We want to be able to cleanly close the network connections between node and server and between client and server. One of the goals is to be able to distinguish between a requested close and an unexpected one. Anoher goal is to enable nodes (and maybe clients) to temporarily disconnect form the server, do their work (i.e. job execution) then reconnect later to send or receive the results.


#2
Comment posted by
lolo4j
Nov 12, 08:56
Implemented in trunk revision 2919

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from New to Closed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.
  • Information about the user working on this issue has been changed, from lolo4j to Not being worked on.