Umm...shouldn't that be 4000? Servers are generally created on a fixed port. Thats why they are called servers...
Ah, I had tried this earlier, and had made a check, with netstat -a, command to find out whether this was available. But, then, it did not create a server.
Tried, this today again, and now it does, create a server on port 4000, but still takes around 7-8 minutes.
Umm...isn't that kinda obvious. If you start it at port 0, it will take a long time to determine a free port.
The reason, I used port 0 is because, I could get the server started on 4000 and Redhat did not make it visible to me whether it had bound some application to that port. Port 0 ultimately, gave a choice to the OS to find out port for me :)
And eewwww...you should've mentioned that you're doing this in Java...
I thought, Java was preferred for networking programming and assumed, this would be true atleast for the years to come by. Is it true?
I dont think you need to do it in Java but you never mentioned which language you were using. So I assumed C.
Ah, for the moment, I don't think, I would be doing it in C, atleast till I am sure, I can do it.
Anyway, try googling the next time. This is the right way to build a client / server:
I do google, a lot more, but solutions seem to be passive, which does seem to help all the time. At these times, I post to the list!
__________________________________________________________ Yahoo! India Matrimony: Find your partner now. Go to http://yahoo.shaadi.com