uptake websocket in place of a socket in atLookup

[purnimavenkatasubbu]

Is your feature request related to a problem? Please describe.

To improve performance

Describe the solution you'd like

To enhance the communication mechanism by using a WebSocket-based connection

Describe alternatives you've considered

No response

Additional context

No response

[gkc]

Note we don't want to replace, but to enhance by providing the option when using AtLookup to create and use websocket connections rather than plain socket connections

[purnimavenkatasubbu]

Changes can be found in the ws_version2

The current issue is that the client closes the WebSocket connection prematurely, without waiting for the server's response. Need to find the root cause for the same.

The same code changes work fine when implemented with Python, but in the Dart implementation (branch [us_Version2]), the client closes the WebSocket connection prematurely, without waiting for the server's response.
https://gist.github.com/purnimavenkatasubbu/31bc98d9c4460a53372ae5bbb89f8e13

[purnimavenkatasubbu]

A working version has been pushed to the branch ws_version.

We are currently working on optimizing the design and have documented three potential approaches in detail
Approaches

[purnimavenkatasubbu]

A new approach has been implemented and changes are pushed to the branch ws_approach1

[purnimavenkatasubbu]

changes are done and PR is ready for review #709

[purnimavenkatasubbu]

Had a call with @gkc , during which Gary suggested refactoring the code by completely removing the outbound connection-related classes and their implementations. I’ve already made the changes and will be raising a new PR to reflect them.