it's probably easier to create and run a proof-of-concept. if you create a set named "test" on the client side, and switch contexts with an EOS method, you would see in the debugger that "test" exists there too. so you can use that set on the server.
you really shouldn't care whether the set "exists on the client memory space", the scope is all that matters. but since the scope of a global set include the EOS/trigger process, I suppose you could say that the content propagates (both ways). 2017/12/06 14:50、Kirk Brooks via 4D_Tech <[email protected]<mailto:[email protected]>> のメール： Help me with this one. Because you're saying I create a set on the client side, let's use 'test' since that's what's on the chart. By the chart 'test' only exists on the client memory space. So if I pass the name of this set to an EOS method then the contents of that set propagate to twin on the server side? ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
