From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom de Vries <tdevries@suse.de>, Tom Tromey <tom@tromey.com>
Subject: Re: [RFC 2/3] [gdb/dap] Allow Content-Length on separate line
Date: Tue, 14 Mar 2023 08:13:39 -0600 [thread overview]
Message-ID: <87ilf3ju98.fsf@tromey.com> (raw)
In-Reply-To: <20230314130535.6369-3-tdevries@suse.de> (Tom de Vries via Gdb-patches's message of "Tue, 14 Mar 2023 14:05:34 +0100")
>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> Also allow:
Tom> ...
Tom> Content-Length: 54
Tom> {"seq": 1, ...}
Tom> Content-Length: 163
Tom> {"seq": 2, ...}
Tom> Content-Length: 136
Tom> ...
Tom> which makes command files a bit easier to read.
Doesn't this violate the XML-RPC protocol? The issue being that the
header is terminated by a blank line, but now this ignores the blank
line. Though of course it's also bad to not have a Content-Length.
Tom
next prev parent reply other threads:[~2023-03-14 14:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 13:05 [RFC 0/3] [gdb/dap] Handle DAP command files Tom de Vries
2023-03-14 13:05 ` [RFC 1/3] [gdb/dap] Add logging of ignored lines Tom de Vries
2023-03-14 14:12 ` Tom Tromey
2023-03-24 8:10 ` Tom de Vries
2023-03-14 13:05 ` [RFC 2/3] [gdb/dap] Allow Content-Length on separate line Tom de Vries
2023-03-14 14:13 ` Tom Tromey [this message]
2023-03-14 15:35 ` Tom de Vries
2023-05-05 13:09 ` Tom Tromey
2023-03-14 13:05 ` [RFC 3/3] [gdb/dap] Allow WAIT_FOR_EVENTS input Tom de Vries
2023-05-05 13:09 ` Tom Tromey
2023-05-05 14:01 ` Tom de Vries
2023-05-10 16:23 ` Tom Tromey
2023-05-10 16:29 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilf3ju98.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).