Re: Serilializing the DOM and passing through nsISocketTransportService.

stony_dreams <[email protected]>
Newsgroups gmane.comp.mozilla.devel.dom
Message-ID <[email protected]>
Hello:

I just changed my socket to BLOCKING and now my Java application reads the
entire DOM and all is going fine. I am also converting the DOM string to
UTF-8 using the nsIScriptableUnicodeConvertor before writing it to the
stream. At the java side I again read the string in UTF-8 format. Still
sometimes I get some wierd text nodes in the DOM after parsing the received
string. These text nodes do not have any of the whitespace characters like
\\t or \\n or \\r and neither the blank spaces as it does not match any of
these characters. But still I am not able to see the characters! I don't
know what the character is so I am not able to remove it too... Any hints
abt what wrong is happening? :confused:
-- 
View this message in context: http://www.nabble.com/Serilializing-the-DOM-and-passing-through-nsISocketTransportService.-tp14953816p14979506.html
Sent from the Mozilla - DOM mailing list archive at Nabble.com.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.