On 6/1/07, Matt Rosin <[EMAIL PROTECTED]> wrote:
Dear Eliot, Thanks, I understand. Probably the stock XML::Simple serializer (outputs in XML is all) will do it then. I was referring to Section 3.2, "Data Manager" in http://www.openlaszlo.org/lps3/docs/deploy/architecture.html where it says, "The Data Manager is comprised of a data compiler that converts all data into a compressed binary format readable by OpenLaszlo applications and a series of data connectors..." I wanted to find information on this compressed format (i.e. is it just gzipped xml?). I have *never* seen a technical document for developers that had the guts to just say "a compressed binary format" without saying what the format was. I expect you don't have to worry about it yourself since it all just works for you, but I I ask because like others I'm worried about the lack in SOLO of this Data Manager and related functionality. Not mainly because I want to use compressed XML but because everything seems so vague the way it is (not) documented. Even more worrisome actually is the next section on the Persistent Connection Manager. Why does it warn me not to use it except without load? It seems the whole point is to use it to reduce load.
As of SWF version 6, the Flash player added a native XML parser that is fast, so we stopped compiling XML on the server, and just pass XML in text form directly to the client. So that binary format is no longer relevant for XML data requests. We still use swf byte code format for the XML-RPC format, because there is no JSON parser available in the flash player, but we pass JSON expressions in OL4 for the DHTML runtime. The details of the binary format are subject to change without notice, and it did not seem worth documenting for external users for this reason. In fact I am in the process of changing the data encoder for SWF XMLRPC to use JSON expressions, compiled via the LPS script compiler, instead of the hand-coded data compiler which is in there now. This will be transparent to end users however.
