[IOTDM-63] Compliance - IoTDM should trigger notification when subscription is set with "net=1" & child resource is created Created: 27/Feb/17 Updated: 15/May/17 Resolved: 15/May/17 |
|
| Status: | Resolved |
| Project: | iotdm |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Anil Pandey | Assignee: | Juraj Kosmel |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 7859 |
| Priority: | High |
| Description |
|
Hi, In our current IoTDM implementation, the notification is triggered for child resource creation/deletion when subscription attribute is set with “net”= 3 But notification should be triggered also for subscriptions with “net” set to 1 because the stateTag of the parent resource had been incremented while creating/deleting child resource. This is special case because creation of contentInstance resource as child resource of the container results in modification (update) of the container resource. Please change the subscription/notification behavior when "net"=1 and child resource is created/deleted. |
| Comments |
| Comment by Juraj Kosmel [ 11/Apr/17 ] |