serversocket

I wrote a client/server Java program using ServerSocket and Socket objects. I then modified the code to use SSLServerSocket and 'SSLSocket` however I am getting different Exceptions thrown including: javax.net.ssl.SSLHandshakeException: no cipher suites in common I am hoping to do as much programmatically as I can. I am also okay with self signed certificates. One tutorial I followed suggested creating a certificate with the keytool java application, then moving that file into your java project. I have done that with the terminal command keytool -genkey -alias zastore -keyalg RSA -keystore za

I've got a bit of an issue and I've been asking regarding it quite a few times, but I think I'm one step closer now, so hopefully someone can help me with the rest. My previous questions: Connect to NAS device from Android How to open files in Android with default viewer using jCIFS Put simply - I want to create an application that: Can connect to a NAS device using jCIFS Is capable of launching files in the default viewer - i.e. a video in the video player The first part is relatively easy and I've already done that, but the second part is what's troubling me and what I've asked about a few

I am using Java.net at one of my project. and I wrote a App Server that gets inputStream from a client. But some times my (buffered)InputStream can not get all of OutputStream that client sent to my server. How can I write a wait or some thing like that, that my InputStream gets all of the OutputStream of client? (My InputStream is not a String) private Socket clientSocket; private ServerSocket server; private BufferedOutputStream outputS; private BufferedInputStream inputS; private InputStream inBS; private OutputStream outBS; server = new ServerSocket(30501, 100); clientSocket = server

What is the most reliable pattern to follow when closing an OutputStream , ServerSocket , or other object that implements the AutoCloseable interface? Should I use try - catch - finally ? Or a shutdown hook. The correct way to use an AutoCloseable instance is with a try -with-resources block, so the resource is reliably closed even if an exception is thrown. Like this: try (OutputStream stream = new ...) { ... // use the resource } catch (IOException e) { ... // exception handling code } You can also control multiple resources using one block (rather than nested blocks): try ( OutputStream