From: Daniel Veillard <veillard@redhat.com>
To: "Mike D. Day" <ncmike@us.ibm.com>
Cc: "Cihula, Joseph" <joseph.cihula@intel.com>,
xen-devel@lists.xensource.com, Stefan Berger <stefanb@us.ibm.com>,
"Scarlata, Vincent R" <vincent.r.scarlata@intel.com>,
Ronald Perez <ronpz@us.ibm.com>
Subject: Re: A migration framework for external devices
Date: Mon, 13 Feb 2006 05:18:39 -0500 [thread overview]
Message-ID: <20060213101839.GF9506@redhat.com> (raw)
In-Reply-To: <43EB6969.6020007@us.ibm.com>
On Thu, Feb 09, 2006 at 11:10:17AM -0500, Mike D. Day wrote:
> Daniel Veillard wrote:
> > So how do you plan to glue the XML and the other parts together ?
>
> One way is to have two channels (like ftp). Have an xml session channel
Urgh, way more complex, you start hitting synchronization problems
requiring more round trips etc ... Maybe the convenience still makes
sense though.
> and a tcp data channel. That gives the benefits of xml-rpc for
> triggering events and invoking plugins. You could use xml-rpc to
> negotiate the port for the migration data transfer, for example. Then
> use the data channel (scp/tcp) for the migration.
>
> I'm not convinced this approach is better than starting from scratch tho.
I can't tell :-) I was just raising a problem which could happen in
the proposal, I still have much to read/learn on the current state...
Daniel
--
Daniel Veillard | Red Hat http://redhat.com/
veillard@redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
next prev parent reply other threads:[~2006-02-13 10:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 20:16 A migration framework for external devices Stefan Berger
2006-02-08 21:28 ` Muli Ben-Yehuda
2006-02-08 21:30 ` Stefan Berger
2006-02-08 22:32 ` Mike D. Day
2006-02-08 22:40 ` Stefan Berger
2006-02-09 12:34 ` Mike D. Day
2006-02-09 15:01 ` Daniel Veillard
2006-02-09 16:10 ` Mike D. Day
2006-02-13 10:18 ` Daniel Veillard [this message]
2006-02-09 16:20 ` Stefan Berger
2006-02-09 16:37 ` Mike D. Day
2006-02-09 15:05 ` Anthony Liguori
2006-02-09 16:52 ` Stefan Berger
2006-02-09 17:05 ` Anthony Liguori
2006-02-09 17:51 ` Stefan Berger
2006-02-09 18:35 ` Mike D. Day
2006-02-09 18:45 ` Anthony Liguori
2006-02-09 18:58 ` Mike D. Day
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=20060213101839.GF9506@redhat.com \
--to=veillard@redhat.com \
--cc=joseph.cihula@intel.com \
--cc=ncmike@us.ibm.com \
--cc=ronpz@us.ibm.com \
--cc=stefanb@us.ibm.com \
--cc=vincent.r.scarlata@intel.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.