Codetown ::: a software developer's community
Hello all:
I am fairly new to the Java world and would like some advice on how to handle rs-232 communications with a Java based GUI I am working on. Several years ago I created a similar GUI with Visual Basic, but my coding skills are a bit rusty and I never got the communication thing completely figured out. I could send command strings easy enough, but I had trouble getting responses and processing them quickly.
The current GUI is to control an RGB lighting system. It has some sliders, some radio buttons, and a few check boxes. When the sliders move a command string needs to be sent out. It will have to happen quickly so that the change in light level is smooth. When the radio buttons and check boxes are clicked, single commands will have to be sent out.
I would also like to be able to handle any responses sent back from the controller. When the sliders are moved, there will be a lot of comm traffic coming back to the GUI. I sure this will require a buffer of some kind, but I am not sure how to set it up.
Once I get the rs-232 option up and running, I need to look at communicating with the light controller via an Ethernet connection.
Any advise or assistance would be appreciated.
Paul Stearns
Tags:
Thanks Nem. I will check those out.
Paul
I took a look at some of the documentation and it seems that RS-232 is not supported for Windows apps anymore. If this is indeed the case, then I guess I need to look at sending communications via Ethernet and using a converter to get it to the RS-232 device.
Any guidance on how to proceed would be appreciated.
Codetown is a social network. It's got blogs, forums, groups, personal pages and more! You might think of Codetown as a funky camper van with lots of compartments for your stuff and a great multimedia system, too! Best of all, Codetown has room for all of your friends.
Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.
Check out the Codetown Jobs group.

Alex Good discusses the fragility of modern cloud-dependent apps and shares a roadmap for "local-first" software. By leveraging a Git-like DAG structure and Automerge, he explains how to move from brittle client-server models to resilient systems where data lives on-device. He explores technical implementation, rich-text merging, and how this infrastructure simplifies engineering workflows.
By Alex Good
Agent workflows make transport a first-order concern. Multi-turn, tool-heavy loops amplify overhead that is negligible in single-turn LLM use. Stateful continuation cuts overhead dramatically. Caching context server-side can reduce client-sent data by 80%+ and improve execution time by 15–29% .
By Anirudh Mendiratta
Birgitta Böckeler discusses the rapid evolution of AI agents, moving beyond "vibe coding" to sophisticated context engineering. She explains how architectural constraints and "harness engineering" create the safety nets required for autonomous code generation. She shares vital insights for leaders on balancing speed with maintainability, security risks, and the cost of AI autonomy.
By Birgitta Böckeler
Spotify's engineering team developed the 2025 "Wrapped Archive," generating 1.4 billion personalized reports for 350 million users. This system identifies key listening days and crafts narratives using a language model. As companies increasingly provide narrative recaps, concerns about user privacy and data tracking persist, necessitating a balance between insights and privacy safeguards.
By Matt Foster
Madelyn Olson discusses the evolution of Valkey's data structures, moving away from "textbook" pointer-chasing HashMaps to more cache-aware designs. She explains the implementation of "Swedish" tables to maximize memory density. She shares insights on systems intuition, memory prefetching, and the rigorous testing needed for mission-critical caches.
By Madelyn Olson
© 2026 Created by Michael Levin.
Powered by