Hello Eugene, > why "new Socket(...)" returns null? Is it something depending of operation system?
new Socket(...) *never* returns null. Either it returns a new socket, or it throws an exception. The reflections stuff in HttpClient 3.x works only on JDK 1.4 and above. On JDK 1.2 or 1.3, it throws an exception about an unknown class or method. You know you're on a higher JDK level, that's why we suggested you should implement a socket factory that uses the 1.4 methods directly instead of going through reflections. hope that helps, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
