User Tools

Site Tools


transformations:sharedmemory

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
transformations:sharedmemory [2021/09/03 18:21] – [Use cases] dmitrytransformations:sharedmemory [2021/09/03 18:23] – [Key-value storage] dmitry
Line 17: Line 17:
 ^ Key ^ Value ^ ^ Key ^ Value ^
 | Path  | D:\Input files  | | Path  | D:\Input files  |
-| Last reload date  | 2021-09-03  |+CustomerDB\Last reload date  | 2021-09-03  |
  
 To obtain a value, one should know the key. Keys and values can be added and removed on demand with the help of the "Shared memory" action. The shared memory is stored in the centralized repository. Therefore any EasyMorph workflow can read (recall) and write (remember) keys and values in the shared memory at any moment as long as it has access to the repository. To obtain a value, one should know the key. Keys and values can be added and removed on demand with the help of the "Shared memory" action. The shared memory is stored in the centralized repository. Therefore any EasyMorph workflow can read (recall) and write (remember) keys and values in the shared memory at any moment as long as it has access to the repository.
  
 +\\
 =====Use cases===== =====Use cases=====
 The shared memory can be convenient in many cases: The shared memory can be convenient in many cases:
transformations/sharedmemory.txt · Last modified: 2023/10/13 23:08 by craigt

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki