Get JSON report via websocket API
See original GitHub issueCurrently I can only know the status of a test result be connecting to /getCaseStatus?casetuple=$case
, but I have no more information about what’s wrong.
Is there any way to fetch the actual JSON report via the web socket client as well? (or even HTTP?)
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Read JSON array from websocket data feed - Stack Overflow
first time json without tbox.data comes, tbox.data is undefined, so you have the error "Cannot read property '0' of undefined".
Read more >Writing WebSocket client applications - Web APIs | MDN
Let's consider the chat client application first alluded to in Using JSON to transmit objects. There are assorted types of data packets the ......
Read more >Get Started Using HTTP / WebSocket APIs - XRPL.org
JSON -RPC uses individual HTTP requests and responses for each call, similar to a RESTful API. You can use any common HTTP client...
Read more >WebSocket & JSON - ESP32 Remote Control with WebSocket
This tutorial details the use of WebSocket to remotely interact with an ESP32 that exposes a web application through an HTTP server.
Read more >How to implement WebSocket API JavaScript application with ...
This article shows how developers may use the JavaScrip Web Workers to implement the WebSocket API web application. It allows the Web Workers...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Awesome, I didn’t know that, thanks!
Yes definitely, if the container can serve those files via HTTP, this is just perfect. I was talking about the absence of such HTTP API, in which case I would have to read the files manually.
Oh. It did look like a websocket API though here: https://github.com/crossbario/autobahn-testsuite/blob/master/autobahntestsuite/autobahntestsuite/fuzzing.py#L309
Totally agreed, and I actually used additional websocket connections for those endpoints (which seemed to work fine on most client implementations I’m testing right now). So now I’m confused as to this HTTP vs websocket controls, it really did look like it worked as a websocket connection 😆 In any case, I will try with the HTTP server, thanks!
yes, those the URLs used when opening the websocket connection, and since every websocket connection starts as HTTP, this is where the confusion comes from. those URLs cannot be used to continue with HTTP/GET after the initial HTTP open.
yes, unfort. that’s how it works (results are just collected in a server class and only updateReports will process that, and process all collected results).