🚀 go-pugleaf

Shankar Unni <shankarunni@netscape.net> wrote:
>lans wrote:
>
>> out.close()
>> in.close()
>> socket.close()
>
>A little bit more information, please?
>
>What are "out" and "in"? Are they connected to the socket? If so, how 
>does your logic do the connection? Every time you open the socket, do 
>you immediately connect "out" and "in" to the socket? If so, you're OK, 
>since you'll get a brand new out and in.
>
>But it's generally good etiquette to close any streams that you open. 
>Also, for sockets, it's polite to shut down the socket cleanly before 
>closing it.  (See Socket.shutdownInput() and Socket.shutdownOutput()).

in and out are IO classes( bufferedreader and print Writer which I use to get a handle to the inout and ooutput stream on the socket.

I then store the socket in a hashtable for later user.  If the server that I'm connected to losses connection then the socket will throw a Socket Exception.  

I then close the socket without closing the stream.  Based on the docs it says when you close a socket then any handle to the scoket is also closed and you have to create a new socket connection.

Is there any real problem not closing the io streams before closing the socket