Author: jsundman Date: 2007-11-13 10:10:01 -0800 (Tue, 13 Nov 2007) New Revision: 7233
Modified: openlaszlo/trunk/docs/src/developers/data-overview.dbk openlaszlo/trunk/docs/src/developers/data-patterns-and-best-practices.dbk openlaszlo/trunk/docs/src/developers/data-replication.dbk openlaszlo/trunk/docs/src/developers/dataprovider.dbk Log: checkpointing data documentation Modified: openlaszlo/trunk/docs/src/developers/data-overview.dbk =================================================================== --- openlaszlo/trunk/docs/src/developers/data-overview.dbk 2007-11-13 17:00:18 UTC (rev 7232) +++ openlaszlo/trunk/docs/src/developers/data-overview.dbk 2007-11-13 18:10:01 UTC (rev 7233) @@ -1,11 +1,4 @@ -<?ignor example role="live-example"> - <title>Runtime constraintes with applyConstraint</title> - <programlisting language="lzx"> - <textobject><textdata fileref="programs/constraints-$1.lzx"/></textobject> - </programlisting> -</example?> - <chapter id="data-overview"> <title>Introduction to Data and Data-Driven Applications</title> Modified: openlaszlo/trunk/docs/src/developers/data-patterns-and-best-practices.dbk =================================================================== --- openlaszlo/trunk/docs/src/developers/data-patterns-and-best-practices.dbk 2007-11-13 17:00:18 UTC (rev 7232) +++ openlaszlo/trunk/docs/src/developers/data-patterns-and-best-practices.dbk 2007-11-13 18:10:01 UTC (rev 7233) @@ -3,7 +3,7 @@ <title>Data Patterns and Best Practices</title> <para> -Data design patterns and best practices +In this chapter we tak a look at some common data design patterns and best practices; that is, how to structure your applications to get the most out of OpenLaszlo's data manipulation capabilities. </para> <section><title>Master Detail</title> <para> Modified: openlaszlo/trunk/docs/src/developers/data-replication.dbk =================================================================== --- openlaszlo/trunk/docs/src/developers/data-replication.dbk 2007-11-13 17:00:18 UTC (rev 7232) +++ openlaszlo/trunk/docs/src/developers/data-replication.dbk 2007-11-13 18:10:01 UTC (rev 7233) @@ -3,40 +3,51 @@ <para> Summary: Earlier chapters contain incidental examples of datareplication; this chapter goes into depth explaining how replicationmanagers are created, the mapping between "clones" and "nodes", lazy replication and pooled replication, etc. It discusses both explicit and replication. Explicit replication is now the recommended style, but it will take a while to phase out implicit replication, so for legacy purposes it must be explained. - -Outline: - -What is data replication? +</para> +<section><title> +What is data replication?</title> +<para> -- A way in which the OL runtime causes new objects to be created according to Xpath queries on a dataset. - -Explicit Replication +</para> +</section> +<section> +<title>Explicit Replication</title> -- The <replicator> tag -- <lazyreplicator> -- <resizereplicator> - -Implicit replication +</section> +<section><title>Implicit replication</title> -- The replicationmanager; its automatic creation -- "lazy" replication -- pooling views - -Data Replication +</section> +<section><title> +Data Replication</title> Simple Replication -- Referencing Clones ---Sorting Clones -- Non-linear Replication - -Selection +</section> +<section><title> +Selection</title> +<para> --setNodes() setNotes() and replication Normally, replication is started when a datapath xpath binding returns multiple nodes. The setNodes() method overides that behavior and forces replication, and replicates over the list of nodes supplied to this function. Note that once this function is called, the replication manager is no longer actively bound to the data it replicates over by its xpath (if it had one); henceforth the replication set can only be controlled by calling setNodes. +</para> +</section> +<section><title> +Checking for "Replication Done"</title> +</section> +<section><title>Lazy Replication</title> +</section> +<section><title>Lazy Replication Syntax</title> +</section> +<section><title>Lazy Performance</title> +</section> +<section><title>Referencing Lazy Clones</title> +</section> -Checking for "Replication Done" - -Lazy Replication -Lazy Replication Syntax -Lazy Performance -Referencing Lazy Clones -</para> </chapter> Modified: openlaszlo/trunk/docs/src/developers/dataprovider.dbk =================================================================== --- openlaszlo/trunk/docs/src/developers/dataprovider.dbk 2007-11-13 17:00:18 UTC (rev 7232) +++ openlaszlo/trunk/docs/src/developers/dataprovider.dbk 2007-11-13 18:10:01 UTC (rev 7233) @@ -2,7 +2,7 @@ <chapter id="dataprovider"> <title>Under the hood: The dataprovider</title> <para> -Summary: This is an advanced topic for people who want to develop alternative protocols. It's used by Laszlo Webtop, for example. +This is an advanced topic for people who want to develop alternative protocols. The dataprovider API provides a way for datasets to use data protocols other than HTTP. By default, mechanisms such as <dataset> and <XMLthat communicate with remoteIt's used by Laszlo Webtop, for example. </para> <section><title>Introduction to dataprovider</title> <para> @@ -12,28 +12,34 @@ Datasets make data requests through dataproviders. The transport mechanism is abstracted away from the dataset. That is, a dataset could use a dataprovider that uses HTTP in one instance, and then swap out to another dataprovider that uses XMPP as its transport as long as the dataprovider can support the dataset's request. </para> <para> -It provides a way for datasets to use data protocols other than HTTP. Enhancements provided by the dataprovider specification will allow clients to set differing data request policies--currently only supported through a server proxy like LPS--like security (e.g., blacklisting and whitelisting of URIs) and transport mechanims (e.g., batching of HTTP requests) +Enhancements provided by the dataprovider specification allow clients to set differing data request policies--currently only supported through a server proxy like LPS--such as security (e.g., blacklisting and whitelisting of URIs) and transport mechanims (for example, batching of HTTP requests). </para> </section> <section><title>The <dataprovider> tag</title> <para> dataprovider --The dataprovider which will handle the dataset's request. - +</para> +<para> multirequest -- True if multiple sequential requests can be made without override previous requests. Default is false for backward compatibility. - +</para> +<para> datarequest -- The current datarequest instance to be used by the dataset to call the dataprovider with. Other methods like setQueryParam() and setSrc() set properties of dataRequest. - -datarequestclass'' The default datarequest class to be used by the dataset. </para> +<para> +datarequestclass -- The default datarequest class to be used by the dataset. +</para> </section> <section><title>New dataset methods</title> <para> -''doRequest( DataRequest )'' behaves the same way as the previous doRequest except a DataRequest instance may be passed in. If passed in, the dataRequest param is used to call into the dataprovider, otherwise the dataset's dataRequest instance is used. +In support of the new dataprovider API, new methods have been added to the <dataset> tag. </para> <para> -''handleResponse( DataRequest )'' the callback handler for doRequest(). +doRequest( DataRequest ) behaves the same way as the previous doRequest except that a dataRequest instance may be passed in. If passed in, the dataRequest param is used to call into the dataprovider. Otherwise the dataset's dataRequest instance is used. </para> +<para> +handleResponse( DataRequest ) --the callback handler for doRequest(). +</para> </section> <section><title> The Data Request Sequence </title> _______________________________________________ Laszlo-checkins mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-checkins
