On Sun, Mar 16, 2014 at 07:01:16PM +0200, Alon Levy wrote:
On 01/12/2014 07:34 PM, Marc-André Lureau wrote:
For example, with qemu, a webdav channel can be created this way:
-chardev spiceport,name=org.spice-space.webdav.0,...
And redirected to a virtio port:
-device
On 01/12/2014 07:34 PM, Marc-André Lureau wrote:
For example, with qemu, a webdav channel can be created this way:
-chardev spiceport,name=org.spice-space.webdav.0,...
And redirected to a virtio port:
-device virtserialport,...,name=org.spice-space.webdav.0
Ack. Still reviewing the
Hi
I would like to push this change, along with the protocol channel
change. I believe the implementation has been around and stable for a
while, and is good enough for inclusion.
This isn't a fundamental change, it's an optional new channel, and as
such I think it shouldn't be any trouble.
On
May be better to avoid hardcoding the port name there using e.g.
static const char * instead?
On Sun, Jan 12, 2014 at 9:34 PM, Marc-André Lureau
marcandre.lur...@gmail.com wrote:
For example, with qemu, a webdav channel can be created this way:
-chardev
For example, with qemu, a webdav channel can be created this way:
-chardev spiceport,name=org.spice-space.webdav.0,...
And redirected to a virtio port:
-device virtserialport,...,name=org.spice-space.webdav.0
---
server/reds.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff
