Le 27/04/2012 21:55, Jeremy White a écrit :
I'd really like to have one but I know I personally can't justify
working on it, if you started doing that it would be great and I'd be
glad to help from the sidelines.
Alright, so it turns out that Emscripten
> I'd really like to have one but I know I personally can't justify
> working on it, if you started doing that it would be great and I'd be
> glad to help from the sidelines.
Alright, so it turns out that Emscripten actually
can be used to do a (presumably intensely slow) port of
the quic library.
On Fri, Apr 06, 2012 at 09:04:21AM -0500, Jeremy White wrote:
> >> Did I miss some implication of the libvirt connection? Can an alternate
> >> client solution be leveraged instead?
> >
> > Not sure what you mean about alternate client solution - alternate to
> > the above? concerning libvirt, it
>> Did I miss some implication of the libvirt connection? Can an alternate
>> client solution be leveraged instead?
>
> Not sure what you mean about alternate client solution - alternate to
> the above? concerning libvirt, it doesn't change anything. Libvirt deals
> with the vm control, setup, mi
On Thu, Apr 5, 2012 at 8:11 AM, Alon Levy wrote:
> of deficiencies compared to a native client:
> * less compression - probably not possible to implement QUIC / ZLIB or
> any other compression that isn't provided by the DOM. (this is from
> the noVNC experience).
I am pretty sure we could us
On Wed, Mar 28, 2012 at 12:05:33PM -0500, Jeremy White wrote:
> I, like many before me, am interested in seeing a spice client on other
> platforms. Things like Mac OS X, iOS, Android, HTML5, and so on.
>
> I've spent a bit of time researching what has gone before, and thought
> I'd try to summar
> And there are already pretty good vnc js clients,
> so why not use that combination, this also enables
> using a native (so non js) client on many more
> machines as there is a vnc client available for
> quite a few platforms.
Sure, but the belief is that the spice protocol is fundamentally
supe
Hi,
Sorry for jumping in in the middle of the thread,
but the whole discussion about a js/html5 client
triggered me to put in my 2 cents:
It already is possible to configure a qemu
vm with both spice and vnc external displays
(which will be mirrors of each other). Not sure
if libvirt allows this
> To be most broadly useful, a HTML5 tunnelled version of SPICE would really
> want to be architected as a proxy, rather than directly in the QEMU SPICE
> server.
Isn't this sort of proxy a well solved problem? That is, can't we
safely presume that we can use an existing proxy or slightly modify
On Thu, Mar 29, 2012 at 03:58:17PM +0200, Attila Sukosd wrote:
> Hi Guys,
>
> I've also been contemplating an alternative html5/js client, and as far as
> I remember, Alon proposed an extension to spice-server to actually contain
> a http server to serve the content to the browser.
> But it seems
Hi Guys,
I've also been contemplating an alternative html5/js client, and as far as
I remember, Alon proposed an extension to spice-server to actually contain
a http server to serve the content to the browser.
But it seems like a too big project to take on alone :)
Best Regards,
Attila
--
I, like many before me, am interested in seeing a spice client on other
platforms. Things like Mac OS X, iOS, Android, HTML5, and so on.
I've spent a bit of time researching what has gone before, and thought
I'd try to summarize what I've found. Mostly that will show my
ignorance and hopefully s
12 matches
Mail list logo
