From 82bd53b80c33194120b91d6e839599510ab8e08e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Florian=20N=C3=BCcke?= Date: Fri, 14 Mar 2014 01:37:29 -0700 Subject: [PATCH] Updated ComponentAccess (markdown) --- ComponentAccess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ComponentAccess.md b/ComponentAccess.md index c85144f..4718c22 100644 --- a/ComponentAccess.md +++ b/ComponentAccess.md @@ -55,7 +55,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 up to one tick (i.e. 50 ms). Just to be clear: this only applies to component APIs. +Some component callbacks can performed as "direct calls". 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 -------