Updated ComponentAccess (markdown)

Florian Nücke 2013-12-26 06:11:53 -08:00
parent 361f241236
commit a8fcaeb995

@ -52,7 +52,7 @@ Note that each primary component you access via `component.getPrimary` or `compo
Direct Calls
------------
Using proxies is generally preferable to `component.invoke`, since proxies can perform "direct calls", if supported by the component; `component.invoke` doesn't. Direct calls are performed in the computer's worker thread, meaning they will return instantly. Normal calls are delegated to the main server thread, to avoid race conditions and other threading issues, which also means that normal calls will take at least one tick (i.e. 50 ms). Just to be clear: this only applies to component APIs.
Using proxies is generally preferable to `component.invoke`, since proxies can perform "direct calls", if supported by the component; `component.invoke` doesn't. Direct calls are performed in the computer's worker thread, meaning they will return instantly. Normal calls are delegated to the main server thread, to avoid race conditions and other threading issues, which also means that normal calls will take up to one tick (i.e. 50 ms). Just to be clear: this only applies to component APIs.
Signals
-------