Is your feature request related to a problem?
Not necessarily a problem but rather, I have a use case for multiple TCP servers that can't be fulfilled with the current ESP-AT.
Describe the solution you'd like.
- Allow creation of multiple TCP servers using AT commands, each specifying a different port.
- Each server instance should:
- Maintain its own connection state and client sessions.
- Be independently startable/stoppable.
- Incoming connections should be associated with their respective server instance and port.
- Existing single-server functionality should remain backward compatible. (Optional)
Describe alternatives you've considered.
- Try changing the protocol from vendor from TCP to UDP
Additional context.
I would like to host an HTTP server with custom endpoints. I don't think that the webserver functionality has this capability.
My idea is to run a TCP server on port 80 and transfer all data received on that port to my host controller which will then handle it.
I would like to host different types of TCP servers on different ports so that my product can interface with multiple different vendor integrations at the same time.
Is your feature request related to a problem?
Not necessarily a problem but rather, I have a use case for multiple TCP servers that can't be fulfilled with the current ESP-AT.
Describe the solution you'd like.
Describe alternatives you've considered.
Additional context.
I would like to host an HTTP server with custom endpoints. I don't think that the webserver functionality has this capability.
My idea is to run a TCP server on port 80 and transfer all data received on that port to my host controller which will then handle it.
I would like to host different types of TCP servers on different ports so that my product can interface with multiple different vendor integrations at the same time.