Forum Discussion
Oct 28, 2008
The reason for this is that the time of writing the Editor there was a bug in the modify_address_class method and it was just easier to delete/add in much the same way the management GUI does (I could be wrong on that though). I'm currently investigating the under-the-cover happenings when classes are modified while iRules are processed that access those classes.
My thought is that the 1000's of folks who are using the iRule Editor with production environments would have reported this if it were an issue - but I could be wrong on that one as well.
One could change the logic to remove the old entries and add new ones with the remove_*_class_member and add_*_class_member functions but that could cause you issues as well as you may find yourself in a state when you've added member 1 and then a request comes in an you haven't added member 2-n yet that you are expecting in the iRule.
As I said, I'm exploring the possible side-effects right now and I'll post them when I do.
-Joe