I am working on an android client which reads continues stream of xml data from my java server via a TCP socket. The server sends a '
' character as delimiter between consecutive responses. Below given is a model implementation..
<response1>
<datas>
<data>
.....
.....
</data>
<data>
.....
.....
</data>
........
........
</datas>
</response1>
<---
acts as delimiter ---/>
<response2>
<datas>
<data>
.....
.....
</data>
<data>
.....
.....
</data>
........
........
</datas>
</response2>
Well I hope the structure is clear now. This response is transmitted from server zlib compressed. So I have to first inflate whatever I am reading from the server, separate on response using delimiter and parse. And I am using SAX to parse my XML
Now my main problem is the xml response coming from server can be very large (can be in the range of 3 to 4 MB). So
to separate responses based on delimiter (
) I have to use a
stringBuilder to store response blocks as it reads from socket
and on some phones StringBuilder cannot store strings in the
MegaBytes range. It is giving OutOfMemory exception, and from
threads like this I got to know keeping large strings (even on a
temporary basis) is not such a good idea.
Next I tried to pass the inflatorReadStream (which in turn takes data
from socket input stream) as the input stream of SAX parser (without
bothering to separate xml myself and relying on SAX's ability to find
the end of document based on tags). This time one response gets
parsed successfully, but then on finding the '
' delimiter SAX
throws ExpatParserParseException saying junk after document
element .
- After catching that ExpatParserParseException I tried to read
again, but after throwing exception SAX Parser closes the stream, so
when I try to read/parse again, it is giving IOException saying
input stream is closed.
A code snippet of what I have done is given below (removed all unrelated try catch blocks for clarity).
private Socket clientSocket = null;
DataInputStream readStream = null;
DataOutputStream writeStream = null;
private StringBuilder incompleteResponse = null;
private AppContext context = null;
public boolean connectToHost(String ipAddress, int port,AppContext myContext){
context = myContext;
website = site;
InetAddress serverAddr = null;
serverAddr = InetAddress.getByName(website.mIpAddress);
clientSocket = new Socket(serverAddr, port);
//If connected create a read and write Stream objects..
readStream = new DataInputStream(new InflaterInputStream(clientSocket.getInputStream()));
writeStream = new DataOutputStream(clientSocket.getOutputStream());
Thread readThread = new Thread(){
@Override
public void run(){
ReadFromSocket();
}
};
readThread.start();
return true;
}
public void ReadFromSocket(){
while(true){
InputSource xmlInputSource = new InputSource(readStream);
SAXParserFactory spf = SAXParserFactory.newInstance();
SAXParser sp = null;
XMLReader xr = null;
try{
sp = spf.newSAXParser();
xr = sp.getXMLReader();
ParseHandler xmlHandler = new ParseHandler(context.getSiteListArray().indexOf(website), context);
xr.setContentHandler(xmlHandler);
xr.parse(xmlInputSource);
// postSuccessfullParsingNotification();
}catch(SAXException e){
e.printStackTrace();
postSuccessfullParsingNotification();
}catch(ParserConfigurationException e){
e.printStackTrace();
postSocketDisconnectionBroadcast();
break;
}catch (IOException e){
postSocketDisconnectionBroadcast();
e.printStackTrace();
e.toString();
break;
}catch (Exception e){
postSocketDisconnectionBroadcast();
e.printStackTrace();
break;
}
}
}
And now my questions are
- Is there any way to make SAX Parser ignore junk characters after on
xml response, and not throw exception and close the stream..
- If not is there any way to avoid out of memory error on
stringBuilder. To be frank,I am not excepting a positive answer on
this. Any workaround?
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…