Skip to content

Better input support through status codes

Right now there is basically one type of input. Text, that can be multilined. From a client standpoint everyone does it the same, a single lined input with the propmpt string displayed. That is status code 10.

There is Status Code 11 which operates like a password field but not very well as the contents is still sent in non-protected way.

My proposal is to provide at least two more input types:

  • 12: Input Text Block
  • 13: Input Binary Data

12 Input Text Block would operate the same as 10 but would be a prompt to the clinet that the input is more than a single line. This would be the difference between a text field and a text area, inputting a single term versus a long block of text. The prompt operates the same as 10.

13 Input Binary Data would be a trigger for selecting a file. Prompt could be a mine type to better select the data. The clinet to server data would include a byte count and then data. Large files would still be handled by file transfer protocols like ftp.

This would allow for both a better UI experience as well as open the protocol to cover more of the basic support of the web. Post comments to a blog post with a client that allows for better visual experience. Uploading an avatar, config file, small images. By making these additional status codes its up to clients to support or not.