From: Jim Blandy <jimb@codesourcery.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb@sourceware.org
Subject: Re: RFC: File transfer commands
Date: Tue, 30 Oct 2007 18:29:00 -0000 [thread overview]
Message-ID: <m3wst478xz.fsf@codesourcery.com> (raw)
In-Reply-To: <20071029204052.GA875@caradoc.them.org> (Daniel Jacobowitz's message of "Mon, 29 Oct 2007 16:40:52 -0400")
Daniel Jacobowitz <drow at false.org> writes:
> On Mon, Oct 29, 2007 at 09:29:41PM +0100, Ulrich Weigand wrote:
>> Hmm, I'd have chosen to use a new target object (TARGET_OBJECT_FILE)
>> and corresponding qXfer packet; the "annex" would obviously be the
>> remote file name.
>>
>> However, that would not support unlink, and it would cause the
>> target to re-open the file for each access. That wouldn't matter
>> for my intended use scenario, not sure if it would in yours ...
>
> Yeah, I did think about using qXfer. Having to close and re-open the
> file isn't a problem for me either, but that didn't allow for other
> useful operations like delete. I haven't implemented any more
> operations than you see here, but it would be a reasonable addition
> to implement "remote ls" - and the corresponding MI commands, which
> might let us use a GUI file browser to select the target program
> to execute.
Yeah, 'remote ls' seems like the logical missing piece. Why not use
'vFile:' as the prefix for delete, and qXfer for read and write?
next prev parent reply other threads:[~2007-10-30 18:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 19:55 Daniel Jacobowitz
2007-10-29 20:29 ` Ulrich Weigand
2007-10-29 20:40 ` Daniel Jacobowitz
2007-10-30 18:29 ` Jim Blandy [this message]
2007-10-30 18:41 ` Daniel Jacobowitz
2007-11-01 0:24 ` Jim Blandy
2007-10-29 23:39 ` Pedro Alves
2007-10-29 23:54 ` Daniel Jacobowitz
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=m3wst478xz.fsf@codesourcery.com \
--to=jimb@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=uweigand@de.ibm.com \
/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).