Improvement #66

Only a class should store network, device and service information

Added by Stefano Lenzi over 7 years ago. Updated about 7 years ago.

Status:New Start date:10/02/2010
Priority:Normal Due date:
Assignee:Stefano Lenzi % Done:

0%

Category:zigbee.basedriver Spent time: -
Target version:org.aaloa.zb4osgi.zigbee.basedriver-1.X Estimated time:12.00 hours
Has a patch:No Has license agreement signed:No

Description

At the moment the data regarding discovered node, devices, and service representing the devices is stored on several classes: Activator, ZigBeeNetwork, and maybe other. We should select only a place for simplify the code.


Related issues

related to Bug #61: Duplicate devices Closed 10/01/2010

Associated revisions

Revision 74
Added by Stefano Lenzi over 7 years ago

Fixed duplicate device discovery ( fixes 61, fixes 50 )
- Added a Test unit for testing
- Created dependencies between ZigBeeNetwork and ZigBeeNodeImpl
- Duplicated devices now should simply updates pre-registered devices
Found the problem of unclear storage of Device information ( refs 66 )

History

#1 Updated by Stefano Lenzi over 7 years ago

  • Target version changed from org.aal-persona.zigbee.basedriver-0.6.0 to unplanned

Deadline for the release has been expired, we will move this to future release considering that the current version has been extensively tested.

#2 Updated by Stefano Lenzi over 7 years ago

  • Target version changed from unplanned to org.aaloa.zb4osgi.zigbee.basedriver-0.7.0

#3 Updated by Stefano Lenzi about 7 years ago

  • Target version changed from org.aaloa.zb4osgi.zigbee.basedriver-0.7.0 to org.aaloa.zb4osgi.zigbee.basedriver-1.X

Moved to the next release cycle

Also available in: Atom PDF