I've been writing code to deal with loss of connections.  It occurs to 
me that isConnected() essentially captures the concept of "was connected 
once.." and does not embody the "is still connected, even now" concept. 
  Am I right in this interpretation of the source code?  Does the 
underlying socket have the wherewithal to provide a real "is still 
connected" status?

-pmr

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
JSch-users mailing list
JSch-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jsch-users

Reply via email to