Symbian3/SDK/Source/GUID-B015C4A3-469E-5AC4-B9B9-A24AF7444E65.dita
changeset 13 48780e181b38
parent 8 ae94777fff8f
--- a/Symbian3/SDK/Source/GUID-B015C4A3-469E-5AC4-B9B9-A24AF7444E65.dita	Fri Jul 16 17:23:46 2010 +0100
+++ b/Symbian3/SDK/Source/GUID-B015C4A3-469E-5AC4-B9B9-A24AF7444E65.dita	Tue Jul 20 12:00:49 2010 +0100
@@ -40,7 +40,7 @@
 is no exposure to Message Server APIs on the client-side. The SendAs Server
 encapsulates the Message Server completely. </p> <fig id="GUID-4B2E7B20-8C11-5E21-ABA1-AA01129A32DC">
 <title>              SendAs architecture            </title>
-<image href="GUID-27EC3C5B-175C-5D27-874C-43D46AA44C08_d0e287704_href.png" placement="inline"/>
+<image href="GUID-27EC3C5B-175C-5D27-874C-43D46AA44C08_d0e292532_href.png" placement="inline"/>
 </fig> </section>
 <section id="GUID-24801AA6-6CDE-584F-A233-F7B68C1C59E3"><title>SendAs Server</title> <p>The <xref href="GUID-BA7B9BA6-B840-5182-90B0-A4914592A40D.dita">SendAs Server</xref> maintains
 all SendAs entries and controls the access to a Message Store. It allows client