I implemented PINE client in Go Lang and during that I found missing information in the standard that I think should be added to avoid any misunderstandings in future:
- endianness, if it is up to emulator (PINE server) to choose endianness, it should be explicitly mentioned
- batch of commands is not atomic which is expected but never mentioned in standard
- if client sends a batch of commands and one of the commands fails, should the server continue with the next commands or terminate execution?
I implemented PINE client in Go Lang and during that I found missing information in the standard that I think should be added to avoid any misunderstandings in future: