From a8fcaeb9952234644db2ca25d4cabee8cf729444 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Florian=20N=C3=BCcke?= Date: Thu, 26 Dec 2013 06:11:53 -0800 Subject: [PATCH] Updated ComponentAccess (markdown) --- ComponentAccess.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ComponentAccess.md b/ComponentAccess.md index 9269255..1950bd6 100644 --- a/ComponentAccess.md +++ b/ComponentAccess.md @@ -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 -------