[Laszlo-dev] serverless operation
bloch at laszlosystems.com
Mon Jan 3 11:58:34 PST 2005
A few comments interspersed.
Oliver Steele wrote:
> [Here's my attempt just to see if I understand the lay of the land. I'll
> give some naming suggestions next.]
> In LPS 2.x, the Laszlo server is used during deployment mode to handle
> these types of requests:
> * *Application requests* (cached, and gzipped), from the browser
> (typically via an HTML <embed>). The server responds with the
> application binary executable (swf).
> * *Media requests* (cached, proxied, transcoded). The server transcodes
> media files (JPEG, PNG, mp3) to a format that the Flash 5 player can
> * *Data requests* (cached, proxied, transcoded). The server compiles XML
> files to a format (ActionScript bytecodes) that the Flash 5 player can
> efficiently parse.
> * *SOAP and XML-RPC requests* (proxied, transcoded). The client doesn't
> actually use SOAP-XML and XML-RPC as the wire format.
> * *JavaRPC requests*. The endpoints of these requests are methods on the
It's also required for use of the <connection> tag.
> The Laszlo server does three things to data and media requests:
> * *Proxying*. The client communicates /directly/ with the server, and
> /indirectly/ with the named endpoint of the request. This replaces Flash
> security limitations with a more configurable set of deployer-specified
> limitations (controlled by an auditable XML file).
The use of the proxy also allows us to control some things that can't be
controlled from the flash client (request headers) and gives us access
to some things that you can't get in the flash client (response
headers). (These features are often used to control cookies).
More information about the Laszlo-dev