Changes for page Volume Mapping (On-premise)
Last modified by Erik Bakker on 2024/08/26 12:37
From version 69.1
edited by Erik Bakker
on 2024/03/05 08:56
on 2024/03/05 08:56
Change comment:
There is no comment for this version
To version 67.1
edited by Erik Bakker
on 2024/02/20 16:50
on 2024/02/20 16:50
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -108,8 +108,6 @@ 108 108 109 109 === 3.3 Temporary file system === 110 110 111 -{{info}}This option is only relevant when running on **Linux**.{{/info}} 112 - 113 113 The temporary file system option is for you if you do not want to work with **persistent** data but require **non-persistent** data. This way, you can increase the container's performance by avoiding writing into the container's writable layer. 114 114 115 115 [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-volume-mapping-on-premise--runtime-volumes-configuration-type-temp-file-storage.png]] ... ... @@ -123,10 +123,6 @@ 123 123 124 124 === 3.4 Named pipe === 125 125 126 -{{info}}This option is only relevant when running on **Windows**.{{/info}} 127 - 128 -A named pipe is a named, one-way or duplex pipe for communication between the pipe server and one or more pipe clients. All instances of a named pipe share the same pipe name, but each instance has its own buffers and handles, and provides a separate conduit for client/server communication. Any process can access named pipes, subject to security checks, making named pipes an easy form of communication between related or unrelated processes. 129 - 130 130 *The named pipe option can be selected, but we yet have to see a valid use case within the context of eMagiz for using this option. Therefore, we won't discuss this option further in this microlearning. 131 131 132 132 {{warning}}