SocketServer | socket server with plugin architecture

Search your code for where the @interface for ESPTaskParameter is defined, that will be in some .h file. Then, make sure the .m file #imports that header file. If it doesn’t the there would indeed be no visible interface defining the selector you want to call to the .m file that is trying to call it

And check that the interface .h does indeed declare a public setter for broadcast.

The error message says all:

Inside the RelayEmulatorApp, after the socketServer has been instantiated, you can assign it to the appDelegate variable.

There are two problems with the response

• The line ending should be \r\n not \n. This is true both for the header as the multipart boundaries and MIME headers in the body. While the browser seems to accept \n for the header (even though this is not standard compliant) it is less forgiving for the multipart MIME body.
• The end of the multipart MIME body is --boundary--\r\n, not --boundary, i.e. the line ending is essential.

This fixes these problems:

request.method is always upper-case.

You'll need

Solved the issue.

Just need to make sure that the route in the NGINX and endpoint configured in stomp must be exactly the same.

For example

NGINX Route:

With socketserver, you would have to implement the websocket protocol in your code. There are several tutorials on the web, e.g. here.

In socket.io v4, you can do:

The hostfwd option is for forwarding connections from the outside world to a server which is running on the guest. "hostfwd=tcp::HOSTPORT-:GUESTPORT" says "QEMU should listen on the host on port HOSTPORT; whenever a connection arrives there, it should forward it to the guest's port GUESTPORT (which hopefully has a server listening there)".

You seem to be running a server on the host. You can't have more than one thing listening on a particular port on one machine, so either the python3 server program can listen on port 28009 and respond to connections there, or QEMU can listen on port 28009 to respond to connections there (forwarding them to the guest), but not both at once. Whichever is started second will complain that something's already using the port.

If you want to run a server on the host and connect to it from the guest, you don't need any QEMU options at all. QEMU's 'usermode' networking will allow guest programs to make connections outwards to any IP address (including the wider internet but also directly to the host), so if you are trying to run a client on the guest and a server on the host that should just work. You can tell the guest client to connect either to the host's real IP address or you can use the special 'gateway' IP address 10.0.2.2 which is how the host machine appears on the fake network that the guest sees.