Einzelnen Beitrag anzeigen

Benutzerbild von jfheins
jfheins

Registriert seit: 10. Jun 2004
Ort: Garching (TUM)
4.579 Beiträge
 
#2

AW: Mailbug in Indy

  Alt 6. Jan 2013, 18:52
Also wenn ich mir das in der RFC mal so angucke:
Zitat:
4.3. String

A string is in one of two forms: either literal or quoted
string. The literal form is the general form of string. The
quoted string form is an alternative that avoids the overhead of
processing a literal at the cost of limitations of characters
which may be used.

A literal is a sequence of zero or more octets (including CR and
LF), prefix-quoted with an octet count in the form of an open
brace ("{"), the number of octets, close brace ("}"), and CRLF.
In the case of literals transmitted from server to client, the
CRLF is immediately followed by the octet data. In the case of
literals transmitted from client to server, the client MUST wait
to receive a command continuation request (described later in
this document) before sending the octet data (and the remainder
of the command).

A quoted string is a sequence of zero or more 7-bit characters,
excluding CR and LF, with double quote (<">) characters at each
end.

The empty string is represented as either "" (a quoted string
with zero characters between double quotes) or as {0} followed
by CRLF (a literal with an octet count of 0).

Note: Even if the octet count is 0, a client transmitting a
literal MUST wait to receive a command continuation request.
Dann ist
1. Die neue Zeile kein Bug sondern gewollt.
2. In den geschweiften Klammern muss stets die Anzahl an Bytes stehen. Hast du da vielleicht irgendwelche Codierungsprobleme, wo mehrere Bytes als ein Buchstabe dargestellt werden? (UTF-8 lässt grüßen)
3. Aus den geschweiften Klammern einen String mit "" zu machen ist wohl eher eine schlechte Idee, weil in den "" nur 7-bit Zeichen stehen dürfen, hinter den Klammern aber volle 8-bit.
  Mit Zitat antworten Zitat