Sockets and BufferedReader

Article View: borland.public.jbuilder.java.language

Article #7610

Back to borland.public.jbuilder.java.language Previous Next

#7610

From: Bill
Date: Wed, 13 Jun 2001 12:56

6 lines
1492 bytes

I've set up a socket connection between a java client and non-java server. To read from the socket I use a bufferedReader object instantiated from an inputStream obtained from the socket. I then use the read(char[], int, int) method to pick up a variable number of characters from the inputStream. Everything works OK -- most of the time. It appears that when the incoming bytes in the stream have values less than 0x80 or greater than 0xA0, the proper value is read. For any value in between the byte value is converted to hex 3F. I suspect it has something to do with the filter classes and the definition of the unicode but haven't been able to find any specifics. Has anyone see this sort of problem?

Thanks

Bill

Technical Details

Message-ID: <3b2762e7$1_1@dnews>

Path:

arc1-ca.pugleaf.net!archiver1.google.com!newsfeed.google.com!sn-xit-02!supernews.com!nntp-relay.ihug.net!ihug.co.nz!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!dnews

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f74b3,f77e393b648464b6,start
X-Google-Attributes: gidf74b3,public
X-Google-ArrivalTime: 2001-06-13 06:12:10 PST
From: "Bill " <shayw@uwgb.edu>
Sender: "Bill " <shayw@uwgb.edu>
Reply-To: "Bill " <shayw@uwgb.edu>
Subject: Sockets and BufferedReader
Newsgroups: borland.public.jbuilder.java.language
X-User-Info: 24.130.236.85 24.130.236.85    
NNTP-Posting-Host: 207.105.83.65
Message-ID: <3b2762e7$1_1@dnews>
Date: 13 Jun 2001 05:56:07 -0700
X-Trace: dnews 992436967 207.105.83.65 (13 Jun 2001 05:56:07 -0700)
Lines: 6
Path: arc1-ca.pugleaf.net!archiver1.google.com!newsfeed.google.com!sn-xit-02!supernews.com!nntp-relay.ihug.net!ihug.co.nz!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!dnews