Hi!
When a device receives the reboot command within the API sometimes doesn’t sends the acknolegment to the application because it rebooted instantly without sending any feedback.
This it’s a suggestion for Mikrotik developers to add a little delay before starting the reboot process after the reception of the command. With that little delay I think the API processor on the device will give some feedback to the application and it will not hang.
Regards,
What acknowledgement do you need since you just reboot the device… just wondering…
I use Chupaka delphi API library.
It sends the commands to the device and the communication library waits an answer from the device after each command it issues.
The problem it’s when the device gets the reboot command it doesn’t answers (it should start the reboot at the same millisecond it receives the command) and the communication library gets stuck until timeout.
communication library waits an answer
This is the part i do not understand… why is it programmed in a way to expect a responce after a reboot command… 
Most likely reboot is not a special case for the library.
I agree it would be nice when the API would first acknowledge the command (and allow some time so it also works over a VPN etc) and then starts the actual reboot.