Timeline for RESTful HTTP and websocket in the same application?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 29, 2016 at 13:36 | vote | accept | Marc | ||
| Apr 29, 2016 at 13:05 | answer | added | maple_shaft♦ | timeline score: 17 | |
| Apr 29, 2016 at 12:57 | comment | added | Marc | @maple_shaft That's good but you need to be on a page with a WebSocket opened to the server. | |
| Apr 29, 2016 at 12:56 | history | edited | Marc | CC BY-SA 3.0 | deleted 15 characters in body |
| Apr 29, 2016 at 12:54 | comment | added | Marc | @EliasVanOotegem Good point. Sorry that wasn't clear. You still have to test the API with a unit project on the server side. What I mean is, if you want a quick look at what the API would return, you can use a broswer with the url. You don't have to write code to open a websocket. I updated my question. | |
| Apr 29, 2016 at 12:54 | comment | added | maple_shaft♦ | Chrome Developer Tools if I am not mistaken allow you to open a websocket and send messages real time | |
| Apr 29, 2016 at 12:53 | history | edited | Marc | CC BY-SA 3.0 | added 44 characters in body |
| Apr 29, 2016 at 12:46 | comment | added | Elias Van Ootegem | "you don't have to write any code to test the API" Could you explain this a bit more? What makes you think you don't have to test the API? | |
| Apr 29, 2016 at 12:29 | history | asked | Marc | CC BY-SA 3.0 |