Very cool. Is now the time to try the experiment of data inheriting from the built-in class? It may take a little work, but look at debug/LzMessage for an example where I subclass String. Basically I had to over-ride all the built-in methods to make it work, because I think the built-in methods take shortcuts (essentially they are `sealed` and don't work for sub-classes, although you just get odd behavior, not an error). Still I think it could be worthwhile to save copying the data.

On 3 Jan 2006, at 23:29, Henry Minsky wrote:

Summary: LPS proxied data loading switched to use Flash client XML parser

New Features: adds lzt=xmldata request type, which returns server- proxied
XML data as XML text

Bugs Fixed:

Technical Reviewer: osteele

QA Reviewer: mdavis

Doc Reviewer:

Documentation:

Release Notes:

Details:

This changeset modifies the LPS server from
using SWF-encoding for data requests to sending the data as XML text
which will be parsed by the client. Thus, the server will be acting
more purely as an XML->XML proxy server.

The LFC will now use the SOLO data loading mechanism (Flash XML Parser) (to
replace the
current mechanism of the server SWF-encoding the XML and loading it with
loadMovie).


This changeset adds two new classes, XMLDataCache and XMLGrabber,
which mirror DataCache and XMLConverter. The lzt=xmldata is similar to
the lzt=data requests, except that instead of encoding the data as
swf, it is returned as the XML text, with HTTP header info included. The XML returned is identical to what is constructed by the existing lzt=data
swf
file, except that namespace information is preserved ( to be compatible with
the
SOLO loading behavior)



--
Henry Minsky
Software Architect
[EMAIL PROTECTED]
_______________________________________________
Laszlo-dev mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-dev

_______________________________________________
Laszlo-dev mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-dev

Reply via email to