[CONTROLLER-227] Websockets: Test & fix data change notifications Created: 24/Mar/14 Updated: 25/Jul/23 Resolved: 04/Jun/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | restconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Milos Fabian | Assignee: | Moiz Raja |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Linux |
||
| Issue Links: |
|
||||||||||||||||
| External issue ID: | 568 | ||||||||||||||||
| Priority: | Low | ||||||||||||||||
| Description |
|
-test data change notification with remote md-sal client |
| Comments |
| Comment by Tom Pantelis [ 30/May/14 ] |
|
This doesn't appear to be IN_PROGRESS seeing that there's been no activity for a while so setting back to CONFIRMED. |
| Comment by Tony Tkacik [ 12/May/15 ] |
|
Tutorial to use websockets. |
| Comment by Jan Hajnar [ 02/Jun/15 ] |
|
Hi, Last week I tested and fixed some bugs in websocket notifications: Notification subscription via test class WebSocketClient, javascript client and SimpleWebsocketClient(Chrome extension) appears to be working fine for container, list and leaf change subscription. So if it is also working for you, could you please mark this bug as resolved? Thanks, |