Jan Ciger wrote: > XML is useful for data definition,
The first two characters of the XML format, "<?", the less-than sign and question-mark, define the data format for further communication. * The data is first read byte by byte. The first two bytes are read and kept in network order, then they are converted to a 16bit value in same network order. That value is then tested to see if it equals ASCII codes for '<' and '?' or '?' and '> in those two orders as a 16 bit value. ** If the either of those tests are true, then the data format is defined as UTF8 for further communication. * If either test false, then then the 16 bit value is test to see if it equals the UTF16 value for '<' or '?'. ** If the UTF16 value is true, then the communication is defined in UTF16 in network order. ** If false, the bytes are swapped and tested for a UTF16 '<' character *** If true, then the communication is defined in UTF16 in opposite of network order (hence, network order is already defined per platform implementation of endianess) * If neither of these are true, then UTF32 could be tested if desired. This is only needed to be done once per initial connection. Again, that sequence does exactly as you expected, which is to define the data format. You continue to say: * not as a network data transfer format. After a successful open tag, it is a pure dedicate network stream as, again, expected. You haven't shown it to do anything more or less than expected, and that is true with the interface and implemention kept distinct from each other. You also say: * I think you should read these What specifically do you want me to know? I started to read it and it quickly went into a wide range of arguments of why people go there to read it. Can you state your thesis? _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/SLDev Please read the policies before posting to keep unmoderated posting privileges
