Home/ Questions/Q 6565765
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T14:08:04+00:00

I am writing a websocket test application that will have a GUI to send

  • 0

I am writing a websocket test application that will have a GUI to send various commands over the websocket. Rather than pack all the control code (message construction, formatting, control) into the callbacks for various controls, I am considering having each GUI element callback (e.g., onClick) send an event to a delegate that can handle it. That way the GUI would be separate from any control code. Is that a ‘sane’ design, or is there another ‘best practice’ to separate the two parts.

An example would be a TV Tuner control — the user can enter a channel number via textbox, which will have no effect until they click the ‘Tune’ button. The onClick method could retrieve the channel number from the textbox, and send a doTune(channel) event to the delegate to make it happen.

Thoughts/advice welcome.

Thank you,
bp

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    This is indeed a sane design. I personally won’t go for an event call, just a regular call to a static ‘SocketCommands’ class will do.

    • 0