Re: [Xen-devel] A migration framework for external devices

["Mike D. Day" <ncmike@xxxxxxxxxx>]

Daniel Veillard wrote:
>   Another common XML related design error is to embbed XML along with
> other data in a stream without markers, you end up having to precompute
> the size of the XML instance which makes streaming impossible or force 
> some unclean processing at the XML level (as an XML instance has no end
> marker in itself, the end must be provided by the container or the code
> driving the parser).
Yes, totally agree

>   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 
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.

Mike

--
LTC Open Hypervisor Project:
1) Ensure linux has a good GPL hypervisor
2) Ensure Xen exploits xSeries Platforms
3) Provide value-add Xen Extensions for IBM customers.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel