amps-python-client 5.3.4.1__zip

amps-python-client-5.3.4.1/docs/python/html/_images/tip.svg

@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!-- Generator: Adobe Illustrator 9.0, SVG Export Plug-In  -->
+<!DOCTYPE svg [
+	<!ENTITY st0 "fill:none;stroke:#000000;stroke-width:1.0944;">
+	<!ENTITY st1 "fill:#FFFFFF;stroke:none;">
+	<!ENTITY st2 "fill-rule:nonzero;clip-rule:nonzero;stroke:#FFFFFF;stroke-width:5.6139;stroke-miterlimit:4;">
+	<!ENTITY st3 "fill:none;stroke:none;">
+	<!ENTITY st4 "fill-rule:nonzero;clip-rule:nonzero;stroke:#000000;stroke-miterlimit:4;">
+	<!ENTITY st5 "stroke:none;">
+]>
+<svg  width="48pt" height="48pt" viewBox="0 0 48 48" xml:space="preserve" xmlns="http://www.w3.org/2000/svg">
+	<g id="Layer_x0020_3" style="&st2;">
+		<g>
+			<path d="M9.5,18.6c0,8,6.5,14.4,14.4,14.4c8,0,14.4-6.5,14.4-14.4c0-8-6.5-14.4-14.4-14.4c-8,0-14.4,6.5-14.4,14.4z M12.8,18.6c0-6.2,5-11.2,11.2-11.2c6.2,0,11.2,5,11.2,11.2c0,6.2-5,11.2-11.2,11.2c-6.2,0-11.2-5-11.2-11.2z"/>
+			<path d="M28.1,37.9l-7.6,0.8c-0.9,0.1-1.5,0.9-1.4,1.8c0.1,0.9,0.9,1.5,1.8,1.4l7.6-0.8c0.9-0.1,1.5-0.9,1.4-1.8c-0.1-0.9-0.9-1.5-1.8-1.4z"/>
+			<path d="M28.1,34.8l-7.6,0.8c-0.9,0.1-1.5,0.9-1.4,1.8c0.1,0.9,0.9,1.5,1.8,1.4l7.6-0.8c0.9-0.1,1.5-0.9,1.4-1.8c-0.1-0.9-0.9-1.5-1.8-1.4z"/>
+			<path d="M28.1,31.6l-7.6,0.8c-0.9,0.1-1.5,0.9-1.4,1.8s0.9,1.5,1.8,1.4l7.6-0.8c0.9-0.1,1.5-0.9,1.4-1.8s-0.9-1.5-1.8-1.4z"/>
+			<path d="M23.1,41.3v0.9c0,0.9,0.7,1.6,1.6,1.6c0.9,0,1.6-0.7,1.6-1.6v-0.9h-3.3z"/>
+			<path style="&st1;" d="M35.9,18.7c0,6.6-5.4,12-12,12c-6.6,0-12-5.4-12-12s5.4-12,12-12c6.6,0,12,5.4,12,12z"/>
+			<path style="&st5;" d="M9.6,18.6c0,8,6.5,14.4,14.4,14.4c8,0,14.4-6.5,14.4-14.4c0-8-6.5-14.4-14.4-14.4c-8,0-14.4,6.5-14.4,14.4z M12.9,18.6c0-6.2,5-11.2,11.2-11.2c6.2,0,11.2,5,11.2,11.2c0,6.2-5,11.2-11.2,11.2c-6.2,0-11.2-5-11.2-11.2z"/>
+			<path style="&st5;" d="M28.2,37.9l-7.6,0.8c-0.9,0.1-1.5,0.9-1.4,1.8c0.1,0.9,0.9,1.5,1.8,1.4l7.6-0.8c0.9-0.1,1.5-0.9,1.4-1.8c-0.1-0.9-0.9-1.5-1.8-1.4z"/>
+			<path style="&st5;" d="M28.2,34.7l-7.6,0.8c-0.9,0.1-1.5,0.9-1.4,1.8c0.1,0.9,0.9,1.5,1.8,1.4l7.6-0.8c0.9-0.1,1.5-0.9,1.4-1.8c-0.1-0.9-0.9-1.5-1.8-1.4z"/>
+			<path style="&st5;" d="M28.2,31.6l-7.6,0.8c-0.9,0.1-1.5,0.9-1.4,1.8c0.1,0.9,0.9,1.5,1.8,1.4l7.6-0.8c0.9-0.1,1.5-0.9,1.4-1.8c-0.1-0.9-0.9-1.5-1.8-1.4z"/>
+			<path style="&st5;" d="M23.1,41.3v0.9c0,0.9,0.7,1.6,1.6,1.6s1.6-0.7,1.6-1.6v-0.9h-3.3z"/>
+			<path style="&st0;" d="M22.3,28.3l-3.5-10.7c0,0,6.6,3.9,10.5,0"/>
+		</g>
+	</g>
+	<g id="crop_x0020_marks" style="&st4;">
+		<path style="&st3;" d="M48,48H0V0h48v48z"/>
+	</g>
+</svg>

amps-python-client-5.3.4.1/docs/python/html/_sources/chapters/advanced-topics.rst.txt

@@ -0,0 +1,398 @@
+
+.. |caution| image:: ../../common/svg/caution.svg
+
+12. Advanced Topics
+====================
+
+Implementing Message Handlers in C or C++
+------------------------------------------
+
+.. index:: message handlers; writing in C++,
+
+The AMPS Python client provides a wrapper
+that works with the python ``ctypes`` module to allow you to create
+message handlers in C or C++ and expose them to Python. This can improve
+performance in the message handler. When you use this technique,
+messages are delivered directly from the C++ client to your message
+handler: there is no Python code involved in handling the messages.
+
+To use this capability, you:
+
+1. Create a message handler with C linkage, and compile that message
+   handler into a shared library
+
+2. In your Python program, use the ``ctypes`` module to load the library
+
+3. Construct an instance of CMessageHandler, a wrapper object that holds
+   a pointer to the message handler function and the userdata to be
+   provided to the handler during each call.
+
+4. Pass the CMessageHandler to any method that expects a message
+   handler.
+
+The AMPS Python client registers the pointer and user data you provide
+as a C++ message handler. Once the handler is registered, no Python code
+is called when providing messages to the handler.
+
+Implementing the Handler
+------------------------
+
+To use this capability, you create a message handler that exposes a
+function with the following signature having C linkage:
+
+.. code:: cpp 
+
+    extern "C"
+    void my_message_handler(
+        AMPS::Message &message,
+        void *userdata
+    );
+
+Notice that this signature is the same signature used by message
+handlers in the AMPS C++ client.You implement the function and compile
+it into a shared library or DLL, using the instructions provided with
+your Python implementation. For details on the C++ client, you can
+install the client itself, or consult the documentation at
+http://docs.crankuptheamps.com/api/cpp/index.html.
+
+Loading and Using the Handler
+-----------------------------
+
+Once you've compiled the library, you use the ``ctypes`` module to load
+the library. You then create an instance of the message handler wrapper,
+and pass that wrapper to the AMPS client methods, as shown below:
+
+.. code:: python
+
+    import ctypes
+    import AMPS
+
+    ...
+
+    # assumes that client is already created and connected
+
+    # load the shared object
+    dll = ctypes.CDLL("./libmymessagehandler.so")
+
+    # create a handler that points to the underlying C function
+    # and bind the user data to that handler. 
+    handler = AMPS.CMessageHandler(dll.my_message_hander, "user data")
+
+    # handler can be used anywhere you would use a message handler
+    client.subscribe(handler, "myTopic")
+
+    client.set_last_chance_message_handler(handler)
+
+    # and so it goes
+
+The ``AMPS.CMessageHandler`` type accepts a pointer to a message handler
+with the signature shown above and a Python object that can be
+marshalled into a native C type through the ``ctypes`` interface. Once
+marshalled, the object will be cast to a ``void *`` and provided in the
+``userdata`` parameter of the message handler. Marshalling the userdata
+parameter follows the ``ctypes`` module conventions. If you need to
+explicitly control the way an object is marshalled, you can construct
+one of the ``ctypes`` objects and pass that new object into the method.
+
+Using the C++ Client
+--------------------
+
+.. index:: calling C++ from Python,
+
+While the AMPS Python client provides enough
+performance for a wide variety of applications, in some cases, using the
+underlying C++ implementation can provide extra performance. The AMPS
+Python client works with the ``ctypes`` module to allow you to pass the
+underlying C++ client to an arbitrary function, effectively allowing you
+to integrate C++ code directly into your Python program.
+
+Consider using the C++ client directly when latency is at a premium or
+when your application works directly with C++. For example, you might
+you use the client directly when:
+
+-  You are assembling messages from a C++ library without a Python
+   binding
+
+-  You need to customize client behavior that is implemented in C++ (for
+   example, implementing a custom SubscriptionManager or BookmarkStore)
+
+-  Your application needs to execute a set of commands with AMPS with
+   minimal latency. For example, you might need to publish an array of
+   values as individual messages with as little latency as possible. In
+   this case, using the underlying C++ client directly can reduce
+   latency.
+
+To use the underlying C++ client, you:
+
+1. Create a function with C linkage, and compile that function into a
+   shared library. One of the parameters of the function should be a
+   reference to an ``AMPS::Client``.
+
+2. In your Python program, use the ``ctypes`` module to load the
+   library.
+
+3. Call the function on the library, passing the appropriate parameters
+   for the C function.
+
+Implementing the C++ Function
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The only requirement on the C++ function is that it have C linkage and
+that one of the parameters is a reference to an ``AMPS::Client``. By
+convention, 60East recommends that the first parameter is the
+``AMPS::Client``. However, this is not a requirement of the interface.
+
+For example, a function that simply takes an ``AMPS::Client`` has the
+following signature:
+
+.. code:: cpp 
+
+    extern "C"
+    void configure_client(AMPS::Client& client);
+
+While a function that takes a client, a topic, and a pointer to data to
+be published might have the following signature:
+
+.. code:: cpp 
+
+    extern "C"
+    void publish_data(
+        AMPS::Client& client,
+        const char * topic,
+        const char * data
+    );
+
+The ``ctypes`` module provides a standard ``AMPS::Client`` to these
+functions. Although the ``Client`` has been created by Python code,
+there is nothing Python-specific about the object within the C++
+function. You can use the Client just as you would any other Client
+object.
+
+You can also use the ``ctypes`` binding with ``AMPS::HAClient``, as
+shown below:
+
+.. code:: cpp 
+
+    extern "C"
+    void install_server_chooser(AMPS::HAClient& client);
+
+Since the ``ctypes`` module passes the data through the C ABI, the module
+is not able to perform extensive type checking on C++ types. Your Python
+code must be careful to pass only objects of the appropriate type, or
+you may cause a segmentation violation. For example, if a method
+expecting an ``HAClient`` receives a ``Client`` and calls
+``connectAndLogon`` (which is not a method provided by Client), your
+program will likely crash.
+
+
+.. caution::
+
+   The ``ctypes`` module has a few important caveats.
+
+   The ``ctypes`` module does not provide strong type-safety    
+   guarantees for C++ classes. It is your responsibility to ensure
+   that you call methods with objects of the appropriate type. 
+
+   The ``ctypes`` module calls your function through an extern "C"
+   interface. C++ exceptions cannot be propagated out of a function
+   with C binding. You must catch all exceptions that may be
+   thrown, or your application will likely crash.
+
+
+
+Loading and Using the Function
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Once you've compiled the library, you use the ``ctypes`` module to load
+the library. You can then call the function directly from Python, using
+the name of the C function and passing the appropriate arguments.
+
+Let's look at a simple example. For this example, assume that you have
+compiled a module named ``module.so`` with the following function:
+
+.. code-block:: cpp
+
+    extern "C" void publish_message(AMPS::Client& client, 
+                                    const char* topic,
+                                    const char* data)
+    {
+        try 
+        {
+            if (&client && topic && data) {
+                client.publish(topic,data);
+            }
+        }
+        catch (AMPS::Exception& e)
+        {
+            /* Handle error reporting and recovery logic */
+        }
+    }
+
+You can load the module and call the function as shown below:
+
+.. code:: python
+
+    import ctypes
+
+    module = ctypes.CDLL("module.so")
+    client = AMPS.Client("client")
+    client.connect("tcp://localhost:9007/amps/json")
+    client.logon()
+
+    module.publish_data(client, "my_topic", "some_data")
+
+The ``ctypes`` module handles type conversions between Python and C
+types. In this case, the module passes the underlying Python client as
+the first argument of the C function. The two Python strings are passed
+as NULL-terminated ``char *`` arrays.
+
+The ctypes module also handles more complicated signatures and correctly
+passes arrays. For example, you could implement a method that publishes
+an array of Python values as follows:
+
+.. code-block:: cpp
+
+    extern "C" void vector_publish(AMPS::Client& client, 
+                                    const char* topic, 
+                                    const char** data, 
+                                    size_t vector_length)
+    {
+        try 
+        {
+            if (topic && &client) {
+                for (;vector_length;--vector_length,++data) {
+                    client.publish(topic,*data);
+                }
+            }
+        }
+        catch (AMPS::Exception& e)
+        {
+            /* Handle reporting and recovery logic */
+        }
+    }
+
+You could then use this function from Python as follows:
+
+.. code:: python
+
+    import ctypes
+
+    module = ctypes.CDLL("module.so")
+    client = AMPS.Client("client")
+    client.connect("tcp://localhost:9007/amps/json")
+    client.logon()
+
+    TOPIC = "topic"
+    DATA  = [{"data":x, "string_data":"string_data"} for x in range(5)]
+
+
+    # initialize vector of data to publish by
+    # dumping the dictionaries to JSON strings
+
+    vector = [json.dumps(data) for data in DATA[1:]]
+
+    # Set up the parameters to be passed to a C
+    # function as explained in the ctype documentation
+    param = (ctypes.c_char_p * len(vector))()
+    param[:] = vector
+
+    # Call the function
+    module.vector_publish(client,TOPIC, param,len(param))                
+
+The sample above creates an array of dictionaries and creates an array
+of JSON objects from those dictionaries.
+
+In this case, it is important for us to control how the array of JSON
+objects is passed to the C function. We need to pass an array of C-style
+strings, that is, ``const char**``. To control how the array is
+marshalled, the sample creates an object that knows how to translate
+between a Python array and ``const char**``, then assigns the array to
+that object (see the ``ctype`` documentation for full details). Once we
+have that object, we simply call the ``vector_publish`` function. None
+of the Python infrastructure is visible to the ``vector_publish``
+function: that function is able to use the provided data as native C++
+data.
+
+Transport Filtering
+--------------------
+
+The AMPS Python client offers the ability to filter incoming and
+outgoing messages in the format they are sent and received on the
+network. This allows you to inspect or modify outgoing messages before
+they are sent to the network, and incoming messages as they arrive from
+the network. This can be especially useful when using SSL connections,
+since this gives you a way to monitor outgoing network traffic before it
+is encrypted, and incoming network traffic after it is decrypted.
+
+To create a transport filter, you create a callable that expects a
+string that contains the raw data, and a direction parameter indicating
+whether the string is output or not. For example, the following function
+simply prints the direction and data:
+
+.. code:: python
+
+    def printing_filter(data, direction):
+        if direction:
+            print("INCOMING ---> %s" % data)
+        else:
+            print("OUTGOING ---> %s" % data)
+
+You then register the filter by calling ``set_transport_filter`` with
+the callable, as shown below.
+
+.. code:: python
+
+    # client is an AMPS client
+    client.set_transport_filter(printing_filter)
+
+Notice that the transport filter function is called with the verbatim
+contents of data received from AMPS. This means that, for incoming data,
+the function may not be called precisely on message boundaries, and that
+the binary length encoding used by the client and server will be presented
+to the transport filter.
+
+
+Working With Binary Data
+----------------------------
+
+A ``Message`` object contains two methods for retrieving the message
+payload:
+
+* ``get_data()`` returns the payload as a string
+* ``get_data_raw()`` returns the payload as bytes
+
+If you are working with binary data that is not guaranteed to be
+valid UTF-8, use the ``get_data_raw`` method to avoid errors
+when attempting to encode the data to a string.
+
+.. index:: SSL, tcps transport,
+
+Using SSL
+---------
+
+The AMPS Python client includes support for Secure Sockets Layer. To use
+this support in the Python client using the default OpenSSL implementation
+for the Python installation, you need only use ``tcps`` for the
+transport type in the connection string.
+
+If your Python client does not have a default OpenSSL implementation,
+you must load an SSL implementation as described following. This is
+typically the case for Windows Python builds, and may be the case if
+your site uses a custom build of Python on Linux.
+
+Loading a Different SSL Implementation
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The Python client also allows you to load and use an OpenSSL implementation
+other than the default implementation for the Python installation. The
+AMPS Python client provides the method ssl_init, which takes the name
+of the library to load or a full path to the file that contains the
+library. For example, to load the SSL implementation at
+``/opt/mycorp/trusted/vetted_ssl.so``, you could use the following line
+of code:
+
+.. code:: python
+
+    AMPS.ssl_init("/opt/mycorp/trusted/vetted_ssl.so")
+
+You must load the SSL library before making the connection.

amps-python-client-5.3.4.1/docs/python/html/_sources/chapters/cpp-compiler-list.rst.txt

@@ -0,0 +1,6 @@
+- Linux: gcc 4.8 or later (recommended), 4.6 or 4.4
+
+- Windows: Visual Studio versions under current mainstream support
+
+- Solaris: Oracle Solaris Studio 12.3
+

amps-python-client-5.3.4.1/docs/python/html/_sources/chapters/cpp-feature-table.rst.txt

@@ -0,0 +1,26 @@
++-----------------------------------+--------------+--------------+--------------+
+|                                   | Linux x64    | Windows x64  | Solaris      |
+|                                   |              |              | SPARC        |
++===================================+==============+==============+==============+
+| Incredible performance            |      X       |      X       |      X       |
++-----------------------------------+--------------+--------------+--------------+
+| Publish and subscribe             |      X       |      X       |      X       |
++-----------------------------------+--------------+--------------+--------------+
+| State of the World (SOW) queries  |      X       |      X       |      X       |
++-----------------------------------+--------------+--------------+--------------+
+| Topic and content filtering       |      X       |      X       |      X       |
++-----------------------------------+--------------+--------------+--------------+
+| Atomic SOW query and subscribe    |      X       |      X       |      X       |
++-----------------------------------+--------------+--------------+--------------+
+| Transaction log replay            |      X       |      X       |      X       |
++-----------------------------------+--------------+--------------+--------------+
+| Historical SOW query              |      X       |      X       |      X       |
++-----------------------------------+--------------+--------------+--------------+
+| Beautiful documentation           |      X       |      X       |      X       |
++-----------------------------------+--------------+--------------+--------------+
+| HA: automatic failover            |      X       |      X       |              |
++-----------------------------------+--------------+--------------+--------------+
+| HA: durable publish and subscribe |      X       |      X       |              |
++-----------------------------------+--------------+--------------+--------------+
+
+**Table 1.1:** *C++ client supported features*

amps-python-client-5.3.4.1/docs/python/html/_sources/chapters/creating-commands.rst.txt

@@ -0,0 +1,159 @@
+10. AMPS Programming: Working with Commands
+===========================================
+
+The AMPS clients provide named convenience methods for core AMPS
+functionality. These named methods work by creating messages and sending
+those messages to AMPS. All communication with AMPS occurs through
+messages.
+
+You can use the ``Command`` object to customize the messages that AMPS
+sends. This is useful for more advanced scenarios where you need precise
+control over the message, or in cases where you need to use an earlier
+version of the client to communicate with a more recent version of AMPS,
+or in cases where a named method is not available.
+
+Understanding AMPS Messages
+---------------------------
+
+AMPS messages are represented in the client as AMPS.Message objects. The
+Message object is generic, and can represent any type of AMPS message,
+including both outgoing and incoming messages. This section includes a
+brief overview of elements common to AMPS command message. Full details
+of commands to AMPS are provided in the *AMPS Command Reference Guide*.
+
+All AMPS command messages contain the following elements:
+
+-  **Command**. The *command* tells AMPS how to interpret the message.
+   Without a command, AMPS will reject the message. Examples of commands
+   include ``publish``, ``subscribe``, and ``sow``.
+
+-  **CommandId**. The *command id*, together with the name of the client,
+   uniquely identifies a command to AMPS. The command ID can be used
+   later on to refer to the command or the results of the command. For
+   example, the command id for a ``subscribe`` message becomes the
+   identifier for the subscription. The AMPS client provides a command
+   id when the command requires one and no command id is set.
+
+Most AMPS messages contain the following fields:
+
+-  **Topic**. The *topic* that the command applies to, or a regular
+   expression that identifies a set of topics that the command applies
+   to. For most commands, the topic is required. Commands such as
+   ``logon``, ``start_timer``, and ``stop_timer`` do not apply to a
+   specific topic, and do not need this field.
+
+-  **Ack Type**. The *ack type* tells AMPS how to acknowledge the message
+   to the client. Each command has a default acknowledgment type that
+   AMPS uses if no other type is provided.
+
+-  **Options**. The ``options`` are a comma-separated list of options
+   that affect how AMPS processes and responds to the message.
+
+Beyond these fields, different commands include fields that are relevant
+to that particular command. For example, SOW queries, subscriptions, and
+some forms of SOW deletes accept the **Filter** field, which specifies
+the filter to apply to the subscription or query. As another example,
+publish commands accept the **Expiration** field, which sets the SOW
+expiration for the message.
+
+For full details on the options available for each command and the
+acknowledgment messages returned by AMPS, see the *AMPS Command
+Reference Guide*.
+
+Creating and Populating the Command
+-----------------------------------
+
+To create a command, you simply construct a command object of the
+appropriate type:
+
+.. code:: python
+
+    command = AMPS.Command("sow")
+
+Once created, you set the appropriate fields on the message. For
+example, the following code creates a sow query, setting the
+command, topic, and filter for the query:
+
+.. code:: python
+
+    command = AMPS.Command("sow")                                   \
+                 .set_topic("messages-sow")                         \
+                 .set_filter("/id > 20")  
+
+When sent to AMPS using the ``execute()`` method, AMPS performs a SOW
+query from the topic ``messages-sow`` using a filter of ``/id > 20``.
+The results of sending this message to AMPS are no different than using
+the form of the ``sow`` method that sets these fields.
+
+Using execute
+-------------
+
+Once you've created a message, use the ``execute`` method to send the
+message to AMPS. One form of the ``execute`` method returns a
+``MessageStream`` that you can use from the calling thread to process
+responses from AMPS. The other form, ``execute_async``, method sends the
+message to AMPS,waits for a ``processed`` acknowledgment, then returns.
+Messages are processed on the client background thread.
+
+For example, the following snippet sends the command created above:
+
+.. code:: python
+
+    client.execute(command)
+
+This returns a ``MessageStream`` identical to the ``MessageStream``
+returned by the equivalent ``client.sow()`` method.
+
+You can also provide a message handler to receive acknowledgments,
+statistics, or the results of subscriptions and SOW queries. The AMPS
+client maintains a background thread that receives and processes
+incoming messages. The call to ``execute_async`` returns on the main
+thread as soon as AMPS acknowledges the command as having been
+processed, and messages are received and processed on the background
+thread:
+
+.. code:: python
+
+    def handleMessages(m):
+       print ("%s : %s" % (m.get_ack_type(), m.get_reason()))
+       # other message handling here
+
+    client.execute_async(command, handleMessages)
+
+While this message handler simply prints the ack type and reason for
+sample purposes, message handlers in production applications are
+typically designed with a specific purpose. For example, your message
+handler may fill a work queue, or check for success and throw an
+exception if the command failed.
+
+Using execute to Publish
+^^^^^^^^^^^^^^^^^^^^^^^^
+
+Notice that the ``publish`` command does not provide typically return
+results other than acknowledgment messages. To send a ``publish``
+command, use the ``execute_async()`` method, providing ``None`` for the
+message handler:
+
+.. code:: python
+
+    client.execute_async(publishCmd, None)
+
+Since the code sets the message handler to ``None``, this code does not
+receive acknowledgments. To detect publish failures, set the
+``FailedWriteHandler`` for the client.
+
+Command Cookbook
+----------------
+
+This section is a quick guide to commonly used AMPS commands. For the
+full range of options on AMPS commands, see the\ *AMPS Command
+Reference*.
+
+.. include:: ./cookbook-publish.inc
+.. include:: ./cookbook-subscribe.inc
+.. include:: ./cookbook-sow.inc
+.. include:: ./cookbook-sow-and-subscribe.inc
+.. include:: ./cookbook-delta-publish.inc
+.. include:: ./cookbook-delta-subscribe.inc
+.. include:: ./cookbook-sow-and-delta-subscribe.inc
+.. include:: ./cookbook-sow-delete.inc