You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, dominh executes KCL commands using the karel/kcl entry point (ie: the controller's web server tunnels requests to the local KCL interpreter and returns the output.
This adds a substantial amount of overhead to every KCL command executed (on the order of 500 ms for a single line of KCL on an R-30iB+), even with the web servers headers disabled.
On many controllers, the KCL console is actually reachable over telnet on tcp://:22. It would make sense to use it in those cases, as typical commands would only take a couple hundred bytes to send and receive the response.
Parsing would be different, as the telnet interface makes quite heavy use of formatting codes, but seems doable.
The text was updated successfully, but these errors were encountered:
Right now,
dominh
executes KCL commands using thekarel/kcl
entry point (ie: the controller's web server tunnels requests to the local KCL interpreter and returns the output.This adds a substantial amount of overhead to every KCL command executed (on the order of 500 ms for a single line of KCL on an R-30iB+), even with the web servers headers disabled.
On many controllers, the KCL console is actually reachable over telnet on
tcp://:22
. It would make sense to use it in those cases, as typical commands would only take a couple hundred bytes to send and receive the response.Parsing would be different, as the telnet interface makes quite heavy use of formatting codes, but seems doable.
The text was updated successfully, but these errors were encountered: