[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] A migration framework for external devices
On Thu, Feb 09, 2006 at 07:34:35AM -0500, Mike D. Day wrote: > adds event and procedural semantics. xml encodings are already defined > for everything we need including bulk data transfers, event semantics, > and remote procedure calls. However, I don't think we should use xml > encodings for bulk data transfer. We could keep that part as it is now. XML for transporting random data is a really bad fit, you need basically to encode it with base64 (or else), it becomes bulky, loose the stucture aspects of XML, and gets really inefficient. 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). So how do you plan to glue the XML and the other parts together ? Daniel -- Daniel Veillard | Red Hat http://redhat.com/ veillard@xxxxxxxxxx | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |