STM32 proxy JSON-RPC server is announced. This is not ready yet, but is already capable of subtracting two numbers.
System task introduced. There will be logging and other system features in future
Logging moved to system task.
Started to implement service description contract. JSON-Schema was introduced...
Started to implement system functionality. Solved logging problem.
Created python script for converting json schema to c language char constant.
system.help method was completed. Now system can send response with service description.
logger_format() function was introduced.
Some refactoring. Double request system fail  was repaired
Java service client was introduced. This will be common client library. CoffeeMachineService interface is a proxy interface to service contract document. AbstractCoffeeMachineService class is general service implementation. API uses java.io.Reader and java.io.Writer abstraction and handles character streams only. Library user must connect service with appropriate character streams using void connect(Reader inputReader, Writer outputWriter) method.
Reader test was added. Readme changed. Some untracked (see .gitignore change) files were added to repo.
JsonRPCMessageHandler class was implemented. It parses json-rpc message and triggers callback methods on service listeners. Some Unit tests were added too.
Started to implement json-rpc service...
Implementation continues. Added response waiter class that will be used in communication operations. Service interface is more general interface than CoffeeMachineService interface, and therefore some general purpose methods were extracted. Some unit tests for new classes are added
RRCResponse now has more tests.
Started to implement request processing. RequestProcessor will handle requests. There will be many different cases how to handle requests. This logic uses Strategy design pattern and service will use only one interface to handle requests. Request proccessing will be in the implementations of RequestProcessor interface.
Started to implement message write logic. There were added a lot of TODO-s. MessageWriterTest.writesRightString should be repaired and writer output should be readed somehow.
Some more tests on MessageWriter were done. Now it handles more general class JSONRPC2Message which is abstract base of all json-rpc messages. JsonRpcCoffeeMachineService test should be added.
Improved tests for json service
Timeout for service was introduced. Now service has timeout which could retrieved or be set using getters and setters. Setter sets service timeout and service request processor timeout too. New rpc requests use processor timeouts. In case of  processor cloning by a new request  old processor timeout is set. Each processor has special waiter object which is waiting for the responce. Waiter has two waiting methods: with timeout parameter and method without timeout. When timeout is not specified waiter uses service timeout( service.getTimeout)