The <canvas> tag has an optional attribute proxied="true|false|inherit", which defaults to "inherit". If proxied="true|false", the application can only be compiled in that mode. It is an error to provide a request parameter with a different compiler setting, and the developer console UI disables options that generate this request. If proxied="inherit", the application is compiled either for proxied or unproxied operation, depending upon the value of a compilation switch (which defaults to unproxied).

In other words, a canvas file may include only library files that have the same value for their proxied attribute, or the (default) value of "inherit". You can't mix and match, and the presence of the <library> proxied attribute is a way to document to developers and to the compiler that a library can only work in one mode of operation.

In proxied applications, all XML data is parsed as it is passed through the OpenLaszlo server. In SOLO applications, XML data is passed directly to the application, and the data is parsed on the client. Because the parser implementations are slightly different in the OpenLaszlo Server and client, the following differences in data handling exist between proxied and SOLO applications. SOLO applications:

Also note that the client system not provide any useful error messages when your data has problems in it, whereas the OpenLaszlo Server can provide clues to what's going on. This another reason why it's best to first develop and test your programs as proxied applications, and then make them SOLO.

There are two ways to compile an application to be deployed SOLO:

The compiler resides in the directory:

3.3.3#/bin

Invoke the compiler with the command:

        lzc filename.lzx 

This will result in creation of the file:

        filename.swf

in same directory as the source. The compiled file can be deployed by any application server, such as apache.

Alternatively you can cause the compilation as a side effect of requesting unproxied deployment, as explained in the next section.

The proxied attribute on the <canvas> tag can take the following values:

The query parameter to the application request URL, for example 'http://lps-3.0/hello.lzx', specifies whether the application is compiled for proxied or unproxied operation. The lzproxied parameter can take the values true and false. If true, the application is proxied by the OpenLaszlo Server. If false, the application is deployed SOLO.

Add a query parameter, 'lzproxied', to the application request URL. For example, 'http://lps-3.0/hello.lzx?proxied=true'. Like the 'debug' query parameter, this parameter acts as a compiler option, and affects the way an application is compiled.

{|
! lzproxied query parameter
!	<canvas proxied=>
!	result
|-
| not present ||	not present ||	proxied
|-
| not present ||	inherit	 || proxied
|-
| not present ||	true ||	proxied
|-
| not present ||	false ||	unproxied
|-
| true	|| not present ||	proxied
|-
| true ||	inherit ||	proxied
|-
| true ||	true ||	proxied
|-
| true ||	false ||	error
|-
| false ||	not present ||	unproxied
|-
| false ||	inherit ||	unproxied
|-
| false ||	true ||	error
|-
| false ||	false ||	unproxied
|}

The existence of the query parameter means that an application can work in either proxied or SOLO mode, can be compiled for either mode without changes to its source code. In particular, this makes it easy to compare the proxied and unproxied operation of an application, and to hold off on committing to the deployment mode for an application.

The existence of the query parameter also makes it possible to implement an HTTP-based user interface (in the form of additional controls on the developer console) for specifying compiler options.

It is also consistent with the debug and runtime target compiler options.

See Chapter 32, Browser Integration for a discussion of how to deploy OpenLaszlo applications within HTML pages. Here's a summary of how this process needs to be modified for SOLO applications.

If you are deploying a SOLO application using LzEmbed and wish to pass parameters down to the application from the base URL, you need to make some modifications to the stock html wrapper page that the server provides.

Here is an lzEmbed line that passes all of the query parameters down to the OpenLaszlo application undamaged:

lzEmbed({url: 'main.lzx.swf?'+window.location.search.substring(1), bgcolor: '#ffffff', width: '100%', height: '100%'});

The thing that's different is the alteration to main.lzx.swf? from main.lzx?lzt=swf and the addition of '+window.location.search.substring(1)'

During development, an HTTP request for a SOLO application that is backed by /path/to/canvas.lzx may cause the compiler to create a file /path/to/canvas.lzx.swf (the object file). Recompilation occurs when all of the following conditions are true:

An HTTP request for a SOLO application returns the object file from the source directory instead of from the OpenLaszlo Server cache.

This is necessary to deploy an application that consists of several deployment files; for example, data and media files in the source directory that are requested during application execution.

You can chose whether or not to make visible the source code to your application. When you want to make sure that your source is not available, do this: