#90 fix: cpl - branch flags not getting initialized correctly

1.5.x
closed-accepted
modules (179)
5
2009-05-09
2009-05-07
No

Hey Bogdan,

This is #2785741 again.

I just updated and it looks like my fix may have been lost in translation. The change which got implemented only partially fixes the problem I'm trying to solve.

Please bare with me while I attempt to explain the issue better. As I understand it (little that I do), the cpl proxy code implements sequential "ordering" by first creating a list of locations (location set). It then removes the first location from the head of the list, attempts to relay it, and then repeats until there are no more locations left in the list (or a positive final response). If additional branch flags are set while processing the first location (in the script branch_route for example), they are not getting cleared when the second location begins to be processed (as branch 0 again). The fix you implemented now initializes the nat branch flag correctly, but doesn't clear other flags that may have been set and these unexpectedly get carried over into for the next location processed. The patch attached completely clears the branch flags each time branch 0 is reused during this process. Note that an example of the correct behavior is implemented in the existing code a few lines down in the loop that add additional branches for parallel processing.

Cheers,

John

Discussion

  • Bogdan-Andrei Iancu

    • assigned_to: nobody --> bogdan_iancu
    • status: open --> closed-accepted
     
  • Bogdan-Andrei Iancu

    Hi John,

    You are right - I overlooked this aspect. Thank you for point this out. I applied the patch in the original form :)

    Thanks and regards,
    Bogdan

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks