Java and Client/Server
Java has some strict security restrictions. An applet can only open a socket to the server on which it was loaded. Applications, on the other hand, are allowed to open sockets to any machine. My client is written as a stand-alone application for this reason. (I don't have access to a web server that will allow me to run my CB server.) There are very few major differences between an applet and an application. An applet extends the class applet and an application extends the class frame. Refer to a book on Java for more specific details.
This project was my first real attempt at client-server programming. I'm hooked! With the basic server written, it is possible to extend the code to do many things. I would like to eventually redesign the user interface to make it look better and be easier to use. Having Linux at home has made the program development process much easier. I was able to use the same tools on both my home system and the Sun workstations at school so a simple recompilation was all that was necessary for the server to run on a Sparc 5. My hope is that someone else will find this work useful. No references could be found in any Java book (I have three) to address this specific application. While client-server applications were available in all of these books, all of the servers were written in Java. Java works well for writing servers, but is not as fast and requires more system resources to run. Every language has its place and Java is no exception. Java is very useful as a client programming language; it's here to stay.
Take a look at the listings:
Java in a Nutshell
David Flanagan (1996, O'Reilly & Associates, Inc)
Java Programming Explorer
Neil Bartlett, Alex Leslie, and Steve Simkin (1996, Coriolis Group Books)
Teach Yourself Java in 21 Days
Lemay and Perkins (1996 Sams.net publishing)
Internetworking with TCP/IP vol III
Comer and Stevens (1993, Prentice-Hall, Inc)
The C Programming Language, second edition
Kernighan and Ritchie (1988, 1978, Prentice Hall)
Various Linux man pages
Joe Novosel (firstname.lastname@example.org) has been an avid computer hobbyist since 1981, when his first computer (Radio Shack Color Computer) had a whopping 4K of memory (including video memory!). He has been using Linux for about two years—since version 1.1.47—and thinks Linux brings back the excitement of his early days in computing. After several years in the electrical trade, Joe decided to return to school and is now a Junior at Georgia Tech, where he pursues a degree in Computer Science.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- August 2015 Issue of Linux Journal: Programming
- Django Models and Migrations
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- The Controversy Behind Canonical's Intellectual Property Policy
- Huge Package Overhaul for Debian and Ubuntu
- Shashlik - a Tasty New Android Simulator
- Embed Linux in Monitoring and Control Systems
- KDE Reveals Plasma Mobile
- diff -u: What's New in Kernel Development