Author: lou
Date: 2007-11-15 00:10:21 -0800 (Thu, 15 Nov 2007)
New Revision: 7284
Modified:
openlaszlo/trunk/docs/src/developers/architecture.dbk
openlaszlo/trunk/docs/src/developers/proxied.dbk
Log:
Change 20071115-lou-h by [EMAIL PROTECTED] on 2007-11-15 04:06:17 AST
in /Users/lou/src/svn/openlaszlo/trunk
for http://svn.openlaszlo.org/openlaszlo/trunk
Summary: remove references to Persistent Connection in dguide
Bugs Fixed: LPP-4978
Technical Reviewer: (pending)
QA Reviewer: (pending)
Doc Reviewer: John Sundman
Details:
Also delete persistent connection code samples that were breaking the build
(checkin in with build 7259):
docs/src/developers/programs/persistent_connection-$3.lzx
docs/src/developers/programs/persistent_connection-$1.lzx
docs/src/developers/programs/persistent_connection-$4.lzx
Tests:
Modified: openlaszlo/trunk/docs/src/developers/architecture.dbk
===================================================================
--- openlaszlo/trunk/docs/src/developers/architecture.dbk 2007-11-15
06:12:37 UTC (rev 7283)
+++ openlaszlo/trunk/docs/src/developers/architecture.dbk 2007-11-15
08:10:21 UTC (rev 7284)
@@ -25,10 +25,11 @@
<itemizedlist spacing="compact"><listitem><para><emphasis
role="em">Proxied</emphasis> applications can do a few things that SOLO
applications cannot do, but they are more trouble to deploy
and sometimes perform more
slowly.</para></listitem><listitem><para><emphasis role="em">SOLO</emphasis>
applications are easier to deploy and sometimes
better-performing.</para></listitem></itemizedlist>
+<!-- fix LPP-4978 IORIO 13 nov 2007 -->
<para>
In many cases you don't need to decide which deployment mode to use until
you're ready to deploy, and the default choice is usually SOLO. In reading the
discussions below,
-keep in mind that when you deploy your applications statically, the run-time
capabilities of OpenLaszlo Server (such as media transcoding and
-the persistent connection manager) will not be available.
+keep in mind that when you deploy your applications statically, the run-time
capabilities of OpenLaszlo Server
+(such as media transcoding) will not be available.
</para>
<para/></section><section><title>Client and Server: Synopsis</title>
<para>
@@ -70,7 +71,9 @@
<para>The OpenLaszlo Server consists of five main subsystems: </para>
-<itemizedlist spacing="compact"><listitem><para>the <glossterm>Interface
Compiler</glossterm></para></listitem><listitem><para>the <glossterm>Media
Transcoder</glossterm></para></listitem><listitem><para>the <glossterm>Data
Manager</glossterm></para></listitem><listitem><para>the <glossterm>Persistent
Connection Manager</glossterm></para></listitem><listitem><para>the
<glossterm>Cache</glossterm></para></listitem></itemizedlist>
+<itemizedlist spacing="compact"><listitem><para>the <glossterm>Interface
Compiler</glossterm></para></listitem><listitem><para>the <glossterm>Media
Transcoder</glossterm></para></listitem><listitem><para>the <glossterm>Data
Manager</glossterm></para></listitem>
+<!-- fix LPP-4978 IORIO 13 nov 2007 -->
+<listitem><para>the
<glossterm>Cache</glossterm></para></listitem></itemizedlist>
<figure><title>OpenLaszlo Server
Architecture</title><mediaobject><imageobject><imagedata
fileref="images/OLServer_services.png"/></imageobject></mediaobject></figure>
@@ -103,17 +106,10 @@
applications and a series of data connectors that enable OpenLaszlo
applications to retrieve data via XML/HTTP. OpenLaszlo applications
can thus interface across the network with databases, XML Web Services, and
Web-server based files or executables.</para>
-<para/></section><section><title condition="swf">The Persistent Connection
Manager</title>
+<para/></section>
+<!-- fix LPP-4978 IORIO 13 nov 2007 -->
-<para>
-In applications compiled to SWF, the Persistent Connection Manager handles
authentication and real-time messaging for OpenLaszlo applications which
require them.
-It provides real-time messaging and notification or data push over HTTP. This
feature does not work in applications compiled to DHTML.</para>
-
-<note><para>This feature is provisional. It works in limited capacity
-situations and is fine to develop with, but we do not recommend
-deployment (with the possible exception of low-capacity, non-mission
-critical deployment) with this feature.</para></note>
-<para/></section><section><title>The Cache</title>
+<section><title>The Cache</title>
<para>The cache contains the most recently compiled version of any
application. The first time an OpenLaszlo application is
requested, it is compiled and the resultant SWF file is sent to the client. A
copy is also cached on the server, so that subsequent
requests do not require waiting for the compilation.</para>
Modified: openlaszlo/trunk/docs/src/developers/proxied.dbk
===================================================================
--- openlaszlo/trunk/docs/src/developers/proxied.dbk 2007-11-15 06:12:37 UTC
(rev 7283)
+++ openlaszlo/trunk/docs/src/developers/proxied.dbk 2007-11-15 08:10:21 UTC
(rev 7284)
@@ -48,12 +48,13 @@
In SOLO deployments, the OpenLaszlo server is not used to mediate between the
OpenLaszlo client application and other services on the web. However, as
explained below, it is possible to use other services to proxy between the
client application and web resources.
</para>
<figure><title>After they have been deployed, SOLO applications do not contact
the OpenLaszlo Server</title><mediaobject><imageobject><imagedata
fileref="images/solo_proxies.png"/></imageobject></mediaobject></figure>
+<!-- fix LPP-4978 IORIO 13 nov 2007 -->
<para>
With OpenLaszlo Server ("proxied") deployment, you place the LZX source (.lzx)
file within the
Web-apps directory of the OpenLaszlo Server. The first time you browse to that
file it is dynamically compiled, and it is automatically recompiled whenever
the source changes. (You refresh the page to force the recompilation.)
OpenLaszlo Server deployment requires a Java Application Server or servlet
container. It provides additional capabilities dependent on the server,
-including support for SOAP, XML-RPC, Java-RPC and persistent connections.
+including support for SOAP, XML-RPC, and Java-RPC.
</para>
<para condition="swf">
In applications compiled to SWF, The OpenLaszlo Server is also required to
transcode resources in media formats that are not
@@ -121,7 +122,9 @@
</para>
<para>
Here is a list of features that require OpenLaszlo Server:</para>
-<itemizedlist spacing="compact"><listitem><para> media types other than SWF,
JPG, or MP3 </para></listitem><listitem><para> Persistent
Connection</para></listitem><listitem><para>
SOAP</para></listitem><listitem><para>XML-RPC</para></listitem><listitem><para>http
response headers in XML requests</para></listitem></itemizedlist>
+<itemizedlist spacing="compact"><listitem><para> media types other than SWF,
JPG, or MP3 </para></listitem>
+<!-- fix LPP-4978 IORIO 13 nov 2007 -->
+<listitem><para>
SOAP</para></listitem><listitem><para>XML-RPC</para></listitem><listitem><para>http
response headers in XML requests</para></listitem></itemizedlist>
<para>
If your application relies on any of these features, you cannot deploy it SOLO.
</para>
_______________________________________________
Laszlo-checkins mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-checkins
