Twilio offers a Java SDK for sending SMS via the Twilio REST API. You would sign up for a Twilio account, then assign a URL to be hit when an incoming portList; private InputStream inputStream = null; private OutputStream outputStream = null; private SerialPort serialPort; String readBufferTrial. Send SMS by using Serial Port (Java API forum at Coderanch)hi., Iam trying to develop a java application that use to pass At Commands to my The wikibook page for Java serial communication () appears to be sending strings with the output method – it is using JavaComms, but I was under the.

Finding Performance Problems It currently takes 16 seconds from pressing run in Eclipse to something appearing on my screen. The first step to fixing this is to find out what is causing the delay. My first assumption would be that it is the hardware on the other end of the connection, but who knows. To figure this out, you can do two things: • Mock the TwoWaySerialComm object, so that there is no real communication with any external device. If your performance problems go away, you know it's not the GUI, but the external device, or the way you communicate with it*. • Profile your code and see which methods take the longest.

Before you don't know what the problem is, it will be hard to suggest improvements. Ups rom patcher. * the communication itself seems to be happening in a different thread, but not the initial connection.

As you say you have performance problems on startup, this might be an issue. Structure It's really good that you put the connection stuff in it's own TwoWaySerialComm class. But right now, this class is hard to use, as you are printing in it, and swallowing exceptions. As you have a GUI, it would be nice to report errors in the GUI, not on the command line. So your TwoWaySerialComm class should throw exceptions instead of printing the errors.

Your fields should also be private and accessed with getters. The biggest problem with your code structure is your GUI class though: It's way too big, and it has a method with 360 lines, which is just way too much. Nobody is going to read or understand that later on, and it makes your code very hard to extend, debug, profile, reuse, etc. This gigantic method also contains a lot of duplication, for example the alarmXButtonActionPerformed ActionListener are pretty much the same. Create an actual class for them, and pass the button as argument. This would already help quite a bit.

If you then extract some of the GUI init code that logically belongs to each other to well-named functions, this would already be a great first step. Misc • your naming could be better in parts. Eg it took me a bit to figure out what gbc_lblParity are.

Don't shorten names, and use java naming conventions (camelCase). ParityLabel and parityGridBagConstraints (or parityConstraints) aren't all that long, but a lot clearer. UPDATE After further review of your code, delay is likely in the getPortIdentifiers(). That is where I'd look first. For purposes of locating the delay, bypass getPortIdentifiers(). You could hard code the device name and to run the code without getting the list.