You are not logged in.
Most probably the answer to my question is in the documentation, but I have not found.
As all communication is stateless I have to worry about dealing with possible connection problems at all locations that the framework will call the server, right?
For example, I have a code responsible for making a change to a table (in client).
if Client.Update(People) then
ShowMessage('Yeah')
else
ShowMessage('Ouch. Something very bad happened. But what really happened?')
The update method returns a boolean telling me if it worked. How do I know what went wrong in case I receive a false response?
Is there any method for me to test if the communication with the server is running?
Offline
Error handling is to be improved.
There is an item on the Roadmap:
Refactor the Client-Server error process, with better transmission of the error raised on server side to identify the cause of a failure on client side;
Offline