Chris, To expand on this a little bit, Storage consists of shared objects only. It's not possible to share objects between clients or a client and the server. Nor would you really want to. Nor would you want to attempt using something like Variable to Variable.
As Lutz points out you can read something in Storage on the server using an EOS method: // myMethod $0:=Storage.someKey You could use the same approach to write to Storage but I would avoid this on the server. This is not what Storage is designed for. I think it would become very sluggish if you were using it extensively especially if you are also writing to it. If you need something like this in your app I would look for a different way to accomplish it. Personally I'd look at some sort of record based solution. On Sun, Sep 9, 2018 at 11:20 PM Chris Belanger via 4D_Tech < [email protected]> wrote: > I am intrigued by the storage object. > > The documentation says that there will be a storage object for the server > and for each client. > > But I have not been able to see an explanation of how you directly use > both. > > So how are they differentiated in code? > > — Thanks > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** -- Kirk Brooks San Francisco, CA ======================= *We go vote - they go home* ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
