YAML, newlines and shell tests about beanstalkd HOT 3 CLOSED

I would be happy with option 1. The protocol spec does not allow clients to assume only LF, it just says that commands produce yaml, so if a client can't handle CF LF pairs, the client is broken. We shouldn't bend over too far to accommodate broken clients.

There's also option 5: keep it the way it is. :) It's not that hard making .expected files, at least not in vim. I understand your point, though. We shouldn't make this unnecessarily hard.

This reminds me of another idea to consider. Reformat responses to use the subset of yaml that is also valid json, and update the protocol doc to say that responses are both json and yaml. The motivation for this goes beyond newline characters, so maybe it's best to leave this for another day.

from beanstalkd.

Ah - it hadn't occurred to me that vim made mixed-newlines so easy, my editor had normalized them to LF, and on top of that I was misinterpreting the false-fails caused by netcat as being newline problems.

So option 5 - keep it the way it is - sounds good to me.

See also my comment on issue #26 regarding a basic python replacement for netcat.

from beanstalkd.

Okay, closing this issue.

from beanstalkd.