[Spice-devel] [PATCH spice-gtk 1/4] tests: add spice+unix:// URI checks

[i iordanov]

If one can infer the usage of unix sockets from other parameters passed
anyway, then there may be no point having it in the first place. For the
VNC URI, we could have gone with vnc+ssh://, or vnc+ssl:// (for stunnel),
but there were ssh-related and stunnel parameters we could infer from so it
became unnecessary.

I already use the VNC RFC spec to provide Red Hat's own movirt a means to
start bVNC via a vnc:// URI intent and aSPICE via an implementation of a
spice:// URI based on the VNC one. I added several parameters like TlsPort,
and renamed the username and password from VncUsername and VncPassword to
SpiceUsername and SpicePassword.

So if you guys want to start from something already in use and seeing
whether extending it works for you, please take a look at parseFomUri()
here:

https://github.com/iiordanov/remote-desktop-clients/blob/master/bVNC/src2/main/java/com/iiordanov/bVNC/ConnectionBean.java

And at the way movirt constructs the URI to start aSPICE and bVNC.

Thanks!
Iordan

On Feb 14, 2018 5:09 AM, "Christophe de Dinechin" <
christophe.de.dinechin at gmail.com> wrote:



> On 13 Feb 2018, at 17:36, Marc-Andre Lureau <mlureau at redhat.com> wrote:
>
> I was not really fond of passing options via URI, but apparently this
> is a standard practice.

So is passing port number after a colon.

Christophe
_______________________________________________
Spice-devel mailing list
Spice-devel at lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/spice-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/spice-devel/attachments/20180215/2a783e4b/attachment.html>