Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blob Error Code & Verbatim Type code question #26

Open
AngusP opened this issue Jul 3, 2019 · 0 comments
Open

Blob Error Code & Verbatim Type code question #26

AngusP opened this issue Jul 3, 2019 · 0 comments

Comments

@AngusP
Copy link
Contributor

AngusP commented Jul 3, 2019

The spec says (for simple errors)

The first word in the error is in upper case and describes the error code. The remaining string is the error message itself. The ERR error code is the generic one. The error code is useful for clients to distinguish among different error conditions without having to do pattern matching in the error message, that may change.

and (for blob errors)

The general form is !<length>\r\n<bytes>\r\n. It is exactly like the String type. However like the Simple error type, the first uppercase word represents the error code.

So am I correct in assuming that the error code must

  1. be upper-case only, or not contain anything other than A-Z0-9-_ or some other limited character set?
  2. be at the start of the error string?
  3. be separated from the rest of the error by a space ?

For the verbatim type, does the 3 character type marker have constraints? I assume it can't be <CR> or <LF>, but perhaps keeping it within the ASCII printable range?

@AngusP AngusP changed the title Blob Error Code question Blob Error Code & Verbatim Type code question Jul 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant