Networking | Forum profile

mgs_saladin wrote: My application does work for public IPs but doesnt work with computers behind NAT as they are in local private networks Sorry, that sentence is meaningless. Even if you replace "NAT" with "router," there's nowhere near enough information provided. Go back and re-read my previous post very carefully. (def. of NAT, as I know it). No. I want to make the application work for those two. Understand from...

Works for me. You must be trying to re-use the socket after it's been closed, like the exception says. You can't do that, you have to create a new Socket.

mgs_saladin wrote: is this true that within same connection on same port the server may respond and send messages to client (that initiated the connection) ? You have a server application accepting TCP socket connections on a publicly available IP address. The server application creates a ServerSocket on the port in question and listens for incoming connections. The client (behind NAT) opens a socket connection to the server. The server...

Yup. Both of those things open something, do something with it, then close it. Then there's no more code for them to execute, so what did you expect to happen? So instead of writing bits of code at random, you should read the Java Networking Tutorial. I could look it up but I will just tell you that the google keywords are "Java Networking Tutorial". Look for the links to Sun tutorials in preference to others.

Okay, a little more progress. The following code effectively captures a jpeg from the camera: URL u = new URL( "http://192.168.1.105/stream.jpg" ); URLConnection uc = u.openConnection(); InputStream s = uc.getInputStream();     File f = new File( "/users/jmock/desktop/streamer2.jpg" ) ; DataOutputStream outdata = new DataOutputStream( new FileOutputStream(f));   while ( true ) {...

Hello, I am working on a Java applet application and would like to choose a Java-based scalable server framework to use within my applcation. I have found a few like xsocket or QuickServer and have a question about other. And, also, which is the one You may advise? Yours sincerely, Slawek

I actually have dedicated lines of 10GB/s, in this case hardware is not the object. I am thinking however of cutting it up into smaller servers, because of the cost. Edited by: Jadz_Core on Nov 27, 2009 1:05 AM

Jadz_Core wrote: The server cycles around 600ms. Each cycle, (assuming a full server, and some moderate action going on) approximately 3GB of data could be written out, and 1.5GB could be read in. (Yes this is a very large application, and the internet usage costs a LOT) Are those numbers correct? An output of 3 GB each 600 ms = 5GB data per second = 40 Gigabit. That's a huge load, I would split that onto more than one server.

Had to change C:\Program Files\Java\jre6\lib\security\java.policy to allow connect to localhost:30000 then all OK.

The simplest design if you have less than 500 clients is to have a cached thread pool with two threads per connection, one for reading and another for writing. Use Executors.newCachedThreadPool(). This will be efficient enough if you keep things simple. You need additional threads to simulate any active content in your game. I suggest you keep these separate.