Do we support the service virtualization of messages being sent via websocket ?
Websockets are their own URI. ws:// instead of http:// (and wss:// instead of https://), so HTTP protocol support won't be useful. It's a way of sending messages over TCP sockets between browser and server, and can be used in real-time browser-based MMOs and protocols like Google Protobuf.
Our TCP socket support should work with some implementations, but websockets can do anything you can think of in TCP, including binary messages and asynchronous bidirectional transmission, and these implementations would currently require a custom Transport Protocol Handler. After all, websockets are useful for streaming more than for services.
Essentially, this explanation means we can't answer the question without knowing what it's being used for.
I assume, Websocket will use HTTP protocol (correct me, if I am wrong). If it uses, HTTP protocol, did you try to vitualize using HTTP protocol header?
Thanks Rick, I've asked the user to confirm what is the case they are covering in order to make an actual study to make a determination if we can virtualize the asset.
Hi Srikanth, Websocket are actually TCP based, so the approach is use TCP virtualization and then make a determination of what type of protocol handler we will used based on the type of information they are handling in the transaction (ODP, SDP, etc)
It's over TCP so you can use the Opaque Data Processor (ODP).
Thanks Stefana, I think that the solution will be TCP and then based on what the type of messages are use ODP or the appropriate Protocol handler..
Retrieving data ...