Member ByteBlower::Logging.File.Name.Set filepath: If the logging file cannot be created or opened (due to permissions or a non-existing path), the user will not be notified of this issue, but logging will not be enabled. Retrieve the filename afterwards to know whether file logging is actually enabled: if the empty string is returned, something went wrong.
Member ByteBlower::Schedules.Start schedules...: HTTP requests are not yet available as a schedulable object and cannot be used with this method.
Member ByteBlower::Tk: Throws arcane Tcl error instead of a clean exception when the TK package is not available.
Member ByteBlowerServer::Update: Since USB interfaces are not yet supported, this method currently has no use. Method is not yet implemented and will throw a technical exception.
Member Layer5.Telnet.Client::Open: When contacting a non-existing or unreachable Telnet server, this application has unexpected behavior. The Layer5.Telnet.Client::Open method returns immediately and TCP moves to the 'active' status. After the timeout expires, TCP moves to the 'finished' status instead of the 'timeOut' status. All the while, data may be sent using Layer5.Telnet.Client::Send. This data is queued during the handshake, but it will not be sent.
Member Layer5.Telnet.Client::Receive: When contacting a non-existing or unreachable Telnet server, this method will not provide an error. When the TCP handshake fails (probably due to timeout), TCP will move (incorrectly) to finished after a while. None of the traffic sent at layer 5 will be received by the Telnet server.
Member Layer5.Telnet.Client::Send data: When contacting a non-existing or unreachable Telnet server, this method will not provide an error. When the TCP handshake fails (probably due to timeout), TCP will move (incorrectly) to finished after a while. None of the traffic sent at layer 5 will be received by the Telnet server.