We were recently driven to drink trying to get an application to talk XML to the embedded Web server in HomeSeer, the home automation application we discussed some weeks ago.We were recently driven to drink trying to get an application to talk XML to the embedded Web server in HomeSeer, the\u00a0home automation application we discussed some weeks ago.The application, written using\u00a0Xcelsius\u00a0from Infommersion, was supposed to send an XML datastream to HomeSeer server via a POST request. The payload of an HTTP POST request follows the header and looks something like this:POST \/test.asp HTTP\/1.1 www.somehost.comHost:User-Agent: Mozilla\/4.0Content-Length: 27Content-Type: application\/x-www-form-urlencodeduserid=bob&password=fishThe payload is everything that comes after the "Content-Type" line. The format of the POST payload should be one or more "variable=value" pairs separated by ampersands.Using Active Server Pages (ASP) code, the browser's POST request is stored in a data structure called the "Form collection." But with HomeSeer there's a limited number of access methods to get to this data, so we used the following:mydata = Request.Form(1)From the POST request detailed above, this code would set mydata equal to "bob" (quotes not included). So, here's an XML datastream that we'll send to a Web server:\u00a0\u00a0 \u00a0\u00a0 A A A\u00a0\u00a0 B B B\u00a0 \u00a0 \u00a0\u00a0 D\u00a0\u00a0 E\u00a0 This is the format of a two-column, two-row table encoded in XML. When the data is accessed through the Form collection using the ASP code above, the contents of mydata will be:"SomeStuff">AAABBBCCCDEFWhat happens is the built-in parsing of POST requests by the Web server assumes the character string "