Re: [lemonade] Lack of text after resp-text-code

[Curtis King <cking at mumbo.ca>]

On 2009-09-07, at 2:25 PM, Timo Sirainen wrote:

> On Sep 7, 2009, at 5:20 PM, Curtis King wrote:
>
> > > From RFC 3501:
> > >
> > > resp-text       = ["[" resp-text-code "]" SP] text
> > > text            = 1*TEXT-CHAR
> > >
> > > So there should always be some text if resp-text-code is used. But  
> > > when
> > > looking at examples in CONDSTORE and QRESYNC RFCs you can see that  
> > > there
> > > is no text:
> > >
> > > S: * OK [HIGHESTMODSEQ 715194045007]
> > > S: * OK [CLOSED]
> > >
> > > I guess these examples are violating RFC 3501 and should be changed?
> >
> > You can't see the text which is a single SP ;-) So, the examples  
> > are correct just not obvious.
>
> No, there also should have been at least one TEXT-CHAR after the  
> space.

I might be wrong as I'm no ABNF expert but I'm sure SP is a valid  
CHAR, so

TEXT-CHAR       = <any CHAR except CR and LF>

from RFC 5234

 CHAR           =  %x01-7F

So sending SP SP CRLF is valid protocol according to the ABNF. The  
example would look like,

* OK [CLOSED]  \r\n

cheers,

ck