Sending strings between two computers via ethernet

A while ago I asked a question about using RS-232 communication with Java.  It seems as though I need to abandon that route because it no longer fits the desired system requirements.  Thanks to Nem for his advice on that one.

 

Now what I need to be able to do is send and receive strings between two computers connected via a network hub.  The computers in use would not be connected to the outside world and would only be communicating with each other at this point.

 

I need to be able to send a string like "auto" terminated with a carriage return when a button on a GUI is pressed by the user.  The GUI would then need to get back a string like "ok" or "err" also followed by a carriage return.

 

I am sure that I am making this much harder than I need to, so if anyone can help out it would appreciated.  For some reason I am having a lot of trouble absorbing how to use Java, so any help or explanations need to be in beginner terms.

 

Thanks.

Views: 2015

▶ Reply to This

Replies to This Discussion

Permalink Reply by Paul Stearns on October 5, 2011 at 10:20am

Thanks, I will check those out.

 

Thanks again for the help.

▶ Reply to Discussion

RSS

Happy 10th year, JCertif!

Notes

Welcome to Codetown!

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.

When you create a profile for yourself you get a personal page automatically. That's where you can be creative and do your own thing. People who want to get to know you will click on your name or picture and…
Continue

Created by Michael Levin Dec 18, 2008 at 6:56pm. Last updated by Michael Levin May 4, 2018.

Looking for Jobs or Staff?

Check out the Codetown Jobs group.

 

Enjoy the site? Support Codetown with your donation.



InfoQ Reading List

Java News Roundup: JDK26-RC2, Payara Platform, Hibernate, Quarkus, Apache Camel, Jakarta EE 12

This week's Java roundup for February 16th, 2026, features news highlighting: the second release candidate of JDK 26; an update on Jakarta EE 12; the February 2026 edition of Payara Platform; a point release of Apache Camel; and maintenance releases of Hibernate Search and Quarkus.

By Michael Redlich

Uforwarder: Uber’s Scalable Kafka Consumer Proxy for Efficient Event-Driven Microservices

Uber has open-sourced uForwarder, a push-based Kafka consumer proxy built to handle trillions of messages and multiple petabytes of data daily. The system introduces context-aware routing, head-of-line blocking mitigation, adaptive auto-rebalancing, and partition-level delay processing to improve scalability, workload isolation, and hardware efficiency in large-scale event-driven microservices.

By Leela Kumili

TSSLint 3.0: Final Major Release with Reduced Dependencies

TSSLint 3, the lightweight TypeScript linting tool by Johnson Chu, enhances performance with a reduced dependencies and improved migration paths from legacy linters. As a spiritual successor to TSLint, it offers near-instant diagnostics and fixes, leveraging native Node support for .ts imports. Enhanced developer tooling and a new TSL compatibility layer simplify linting in large-scale projects.

By Daniel Curtis

Podcast: Software Evolution with Microservices and LLMs: A Conversation with Chris Richardson

In this podcast, Michael Stiefel spoke with Chris Richardson about using microservices to modernize software applications and the use of artificial intelligence in software architecture. We first discussed the problems of monolithic enterprise software and how to use microservices to evolve them to enable fast flow - the ability to achieve rapid software delivery.

By Chris Richardson

Article: Building a Least-Privilege AI Agent Gateway for Infrastructure Automation with MCP, OPA, and Ephemeral Runners

This article presents a least-privilege AI Agent Gateway that places clear controls between AI agents and infrastructure. Agents do not access infrastructure APIs directly. Instead, every request is validated, authorized using policy as code with Open Policy Agent (OPA), and executed in short-lived, isolated environments, with built-in observability using OpenTelemetry.

By Nabin Debnath

© 2026   Created by Michael Levin.   Powered by

Badges  |  Report an Issue  |  Terms of Service