Merge commit 'a058e55c06a172b2a6acfa54e8a6f79d38fad564' into HEAD

embdur · Mar 25, 2017 · d682424 · d682424
2 parents c7d8349 + a058e55
commit d682424
Show file tree

Hide file tree

Showing 10 changed files with 416 additions and 485 deletions.
diff --git a/core/devdoc/control_message_requirements.md b/core/devdoc/control_message_requirements.md
@@ -11,7 +11,7 @@ both the C structures and the corresponding serialized structure is given in
 
 ## References
 
-[On out process gateway modules](on-out-process-gateway-modules.md)
+[On out process gateway modules](outprocess_hld.md)
 
 [Control messages in out process modules](out-process-control-messages.md)
 

diff --git a/core/devdoc/on-out-process-gateway-modules.md b/core/devdoc/on-out-process-gateway-modules.md
diff --git a/core/devdoc/out-process-control-messages.md b/core/devdoc/out-process-control-messages.md
@@ -98,7 +98,7 @@ Create message
 
 The *create* message is sent by the gateway to the module host process to
 indicate that the remote module should be loaded and instantiated. The [high
-level design document](./on-out-process-gateway-modules.md) specifies what this
+level design document](./outprocess_hld.md) specifies what this
 message should be composed of. The `type` field will have the value
 `CONTROL_MESSAGE_TYPE_MODULE_CREATE` and the body of the message will be a struct that
 looks like this (as specified in the high level design document):

diff --git a/core/devdoc/outprocess_hld.md b/core/devdoc/outprocess_hld.md
diff --git a/core/devdoc/outprocess_loader_requirements.md b/core/devdoc/outprocess_loader_requirements.md
@@ -8,7 +8,7 @@ The out of process (outprocess) module loader implements loading of gateway modu
 
 ## References
 [Module loader design](./module_loaders.md)
-[Out of Process Module HLD](./on-out-process-gateway-modules.md)
+[Out of Process Module HLD](./outprocess_hld.md)
 [Out of Process Module requirements](./outprocess_module_requirements.md)
 
 ## Exposed API

diff --git a/core/devdoc/outprocess_module_requirements.md b/core/devdoc/outprocess_module_requirements.md
@@ -4,7 +4,7 @@ Binding for Out of Process Azure IoT Gateway Modules
 Overview
 --------
 
-This document specifies the requirements for the gateway module that manages a module running out of process.  The module communicates to the remote module via the inter-process transport mechanism.  The [high level design](../../core/devdoc/on-out-process-gateway-modules.md) will provide an overview on how this module communicates to the module host process.
+This document specifies the requirements for the gateway module that manages a module running out of process.  The module communicates to the remote module via the inter-process transport mechanism.  The [high level design](../../core/devdoc/outprocess_hld.md) will provide an overview on how this module communicates to the module host process.
 
 Types
 -----
@@ -32,7 +32,7 @@ extern const MODULE_API_1 Outprocess_Module_API_all =
 
 ## References
 
-[On out process gateway modules](on-out-process-gateway-modules.md)
+[On out process gateway modules](outprocess_hld.md)
 
 [Control messages in out process modules](out-process-control-messages.md)
 

diff --git a/proxy/modules/native_module_host/devdoc/native_module_host.md b/proxy/modules/native_module_host/devdoc/native_module_host.md
@@ -104,7 +104,7 @@ MODULE_EXPORT const MODULE_API* MODULE_STATIC_GETAPI(OOP_MODULE_HOST)(MODULE_API
 References
 ----------
 
-[On out process gateway modules](on-out-process-gateway-modules.md)
+[Outprocess High-Level Design](outprocess_hld.md)
 
 
 Module\_GetApi

diff --git a/proxy/outprocess/devdoc/launcher.vsdx b/proxy/outprocess/devdoc/launcher.vsdx
diff --git a/samples/native_module_host_sample/README.md b/samples/native_module_host_sample/README.md
@@ -4,7 +4,7 @@ This document provides an overview of the out of process module [code](./src) wh
 
 ##Concepts
 
-This is an extension on the [out of process module example](../proxy_sample/README.md), the native module host allows a user to take an existing gateway module (including bindings) and run it in an external process. For details, please read the [high level design on out of process modules](../../core/devdoc/on-out-process-gateway-modules.md).
+This is an extension on the [out of process module example](../proxy_sample/README.md), the native module host allows a user to take an existing gateway module (including bindings) and run it in an external process. For details, please read the [outprocess high level design](../../core/devdoc/outprocess_hld.md).
 
 
 There are two executables "native\_gateway" and "native\_host\_sample". The "native\_gateway" is a gateway executable with an out of process module, and "native\_host\_sample" is the executable which implements the out of process module.

diff --git a/samples/proxy_sample/README.md b/samples/proxy_sample/README.md
@@ -4,7 +4,7 @@ This document provides an overview of the out of process module [code](./src) wh
 
 ##Concepts
 
-Until this feature, all gateway modules were required to run in the same process as the gateway executable. Now, the user may define a module that runs in a different process on the same machine.  For details, please read the [high level design on out of process modules](../../core/devdoc/on-out-process-gateway-modules.md).
+Until this feature, all gateway modules were required to run in the same process as the gateway executable. Now, the user may define a module that runs in a different process on the same machine.  For details, please read the [outprocess high level design](../../core/devdoc/outprocess_hld.md).
 
 There are two executables "proxy\_sample" and "proxy\_sample\_remote". The "proxy\_sample" is a gateway executable with an out of process module, and "proxy\_sample\_remote" is the executable which implements the out of process modules.