[geode] branch develop updated: GEODE-3745 User Guide: Incomplete diagram, durable client

[db...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

dbarnes pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode.git


The following commit(s) were added to refs/heads/develop by this push:
     new 2affe0f  GEODE-3745 User Guide: Incomplete diagram, durable client
2affe0f is described below

commit 2affe0f120d5d72bd72e3725153cb68fb818b845
Author: Dave Barnes <db...@pivotal.io>
AuthorDate: Wed Jan 17 13:40:24 2018 -0800

    GEODE-3745 User Guide: Incomplete diagram, durable client
---
 ...ementing_durable_client_server_messaging.html.md.erb |   2 +-
 geode-docs/images/ClientServerAdvancedTopics-6.gif      | Bin 12056 -> 0 bytes
 geode-docs/images/ClientServerAdvancedTopics-6.png      | Bin 0 -> 22878 bytes
 3 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/geode-docs/developing/events/implementing_durable_client_server_messaging.html.md.erb b/geode-docs/developing/events/implementing_durable_client_server_messaging.html.md.erb
index a1d1792..9696219 100644
--- a/geode-docs/developing/events/implementing_durable_client_server_messaging.html.md.erb
+++ b/geode-docs/developing/events/implementing_durable_client_server_messaging.html.md.erb
@@ -173,7 +173,7 @@ During initialization, the client cache is not blocked from doing operations, so
 
 This figure shows the three concurrent procedures during the initialization process. The application begins operations immediately on the client (step 1), while the client’s cache ready message (also step 1) triggers a series of queue operations on the servers (starting with step 2 on the primary server). At the same time, the client registers interest (step 2 on the client) and receives a response from the server. Message B2 applies to an entry in Region A, so the cache listener handles [...]
 
-<img src="../../images/ClientServerAdvancedTopics-6.gif" alt="Durable client reconnection. " id="implementing_durable_client_server_messaging__image_068A59FA019E46FA9DE0BC7FA60AAADD" class="image" />
+<img src="../../images/ClientServerAdvancedTopics-6.png" alt="Durable client reconnection. " class="image" />
 
 ## <a id="implementing_durable_client_server_messaging__section_C848DF6D649F4DCAA2B895F5439BAA97" class="no-quick-link"></a>Durable Event Replay
 
diff --git a/geode-docs/images/ClientServerAdvancedTopics-6.gif b/geode-docs/images/ClientServerAdvancedTopics-6.gif
deleted file mode 100644
index 0191a6c..0000000
Binary files a/geode-docs/images/ClientServerAdvancedTopics-6.gif and /dev/null differ
diff --git a/geode-docs/images/ClientServerAdvancedTopics-6.png b/geode-docs/images/ClientServerAdvancedTopics-6.png
new file mode 100644
index 0000000..2e8e237
Binary files /dev/null and b/geode-docs/images/ClientServerAdvancedTopics-6.png differ

-- 
To stop receiving notification emails like this one, please contact
['"commits@geode.apache.org" <co...@geode.apache.org>'].