mtconnect
Main websocket fixes 3
update to correct the issue "Webocket does not respond to asset or assets request #578" #580
It does require adding an additional websocket command "assetsById". I was actually considering expanding my current Websocket program to test all of the Websocket Functionality.
I would like to build a test framework so we can also run it headless like we do with the REST requests. It would bypass the connection and upgrading to websockets and just send the JSON commands directly through to the parser and dispatcher. This will make it easier to validate that all the routes are working correctly.
Got you. I was going to take a look at doing something similar to that. I had intended to make the Shop Floor meeting this morning but had to take care of some other personal business.
From: William Sobel @.> Sent: Wednesday, December 17, 2025 5:06 AM To: mtconnect/cppagent @.> Cc: David Wickelhaus @.>; Author @.> Subject: Re: [mtconnect/cppagent] Main websocket fixes 3 (PR #586)
[https://avatars.githubusercontent.com/u/1302665?s=20&v=4]wsobel left a comment (mtconnect/cppagent#586)https://github.com/mtconnect/cppagent/pull/586#issuecomment-3664611354
I would like to build a test framework so we can also run it headless like we do with the REST requests. It would bypass the connection and upgrading to websockets and just send the JSON commands directly through to the parser and dispatcher. This will make it easier to validate that all the routes are working correctly.
— Reply to this email directly, view it on GitHubhttps://github.com/mtconnect/cppagent/pull/586#issuecomment-3664611354, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC4DQ4NHKWZRTXMPHYFL3ZD4CETJJAVCNFSM6AAAAACPDU4RPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNRUGYYTCMZVGQ. You are receiving this because you authored the thread.Message ID: @.@.>>