Format for lists and dictionary responses #615
Labels
FeatureRequest
Unplanned
Issue is not planned for some reason, such as complexity, lack of clarity, or low priority.
Originally posted by @kr in #610 (comment)
I've thought some more on this and I think going either the YAML or the JSON road is troublesome unless you want to pull in a proper library into beanstalkd.
We could actually simplify the formats as well, since the beanstalkd protocol is a text based protocol and requires a custom parser / interpreter it's not much work to define the lists and dictionaries.
Lists:
\n
This gives you all you need to know, no parsing and more importantly no escaping required.
Dictionary:
a-z
and the character-
.:
These could have trivial implementations in beanstalkd code and to not break existing clients we could implement these as new commands. For example
stats-tubes-2
orstats-2
.For me this has no priority by the way, I'm happy parsing the YAML in it's current state and since I'm assuming developers create tube names in a reasonable way (not containing user input) it should cause no issues.
The text was updated successfully, but these errors were encountered: