Changes between Version 22 and Version 23 of Internal/NewNodeAgent
- Timestamp:
- Feb 24, 2015, 12:32:37 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Internal/NewNodeAgent
v22 v23 247 247 [[Image(HwDiscover - New Page.png, 700px)]] 248 248 ---- 249 12/19/2015249 2/19/2015 250 250 251 251 Tow major discrepencaies were discovered when during the last expirement run. … … 274 274 * Passive: 275 275 * configure 276 276 ---- 277 2/23/2015 278 279 There is a logical loop that could potentially happen. The issue is that settings have to be applied in order. If several settings are stored before the call to connect goes out, there may be a loop introduced by calling configure from connect. The solution is build a new function called by both configure and connect called apply_config. It will check the config and impose and ordering on the properties (stored in an ordered has). 280 281 Configure should have the following logic: 282 283 if connected: 284 disconnect 285 connect 286 287 Where connect does: 288 289 apply_config 290 connect 291 292 apply_config should maintain an the order of the settings. (maybe connect can / should do this)