Re: [Spice-devel] [spice-common 7/8] quic: Remove test which is always TRUE

2014-01-07 Thread Christophe Fergeau
On Tue, Jan 07, 2014 at 01:47:12PM +0100, Christophe Fergeau wrote: > Hey, > > On Mon, Jan 06, 2014 at 03:35:24PM +0200, Uri Lublin wrote: > > On 01/06/2014 01:22 PM, Christophe Fergeau wrote: > > >find_model_params() is first dereferencing nbuckets when setting > > >it to 0, and then it checks it

Re: [Spice-devel] [spice-common 7/8] quic: Remove test which is always TRUE

2014-01-07 Thread Christophe Fergeau
Hey, On Mon, Jan 06, 2014 at 03:35:24PM +0200, Uri Lublin wrote: > On 01/06/2014 01:22 PM, Christophe Fergeau wrote: > >find_model_params() is first dereferencing nbuckets when setting > >it to 0, and then it checks it for NULL. The NULL-check will never trigger > >as if the pointer was NULL, we'd

[Spice-devel] [PATCH 09/17] Add RedsStream::priv

2014-01-07 Thread Christophe Fergeau
The private data is allocated at the same time as RedsStream and goes immediatly after the main RedsStream data. This private member will allow to hide internal RedsStream implementation details from the rest of spice-server. --- server/reds_stream.c | 6 +- server/reds_stream.h | 4 2 fi

[Spice-devel] [PATCH 11/17] Make RedsStream::ssl private

2014-01-07 Thread Christophe Fergeau
--- server/reds_stream.c | 35 ++- server/reds_stream.h | 1 - 2 files changed, 18 insertions(+), 18 deletions(-) diff --git a/server/reds_stream.c b/server/reds_stream.c index 95c159f..f558897 100644 --- a/server/reds_stream.c +++ b/server/reds_stream.c @@ -34,6

[Spice-devel] [PATCH 12/17] Make RedsStream read/write functions private

2014-01-07 Thread Christophe Fergeau
--- server/reds_stream.c | 33 +++-- server/reds_stream.h | 5 - 2 files changed, 19 insertions(+), 19 deletions(-) diff --git a/server/reds_stream.c b/server/reds_stream.c index f558897..7f6172f 100644 --- a/server/reds_stream.c +++ b/server/reds_stream.c @@ -35,

[Spice-devel] [PATCH 02/17] Add reds_stream.[ch]

2014-01-07 Thread Christophe Fergeau
Gather common RedsStream code there rather than having it in reds.c --- server/Makefile.am | 2 + server/inputs_channel.c | 1 + server/red_channel.c| 1 + server/red_channel.h| 2 +- server/red_worker.c | 1 + server/reds.c | 181 +-

[Spice-devel] [PATCH 06/17] Move stream read/write callbacks to reds_stream.c

2014-01-07 Thread Christophe Fergeau
Now that stream creation and SSL enabling are done by helpers in reds_stream.c, we can move the initialization of the vfunc read/write pointers there too. --- server/reds.c| 77 server/reds_stream.c | 75 +

[Spice-devel] [PATCH 14/17] Make RedsStream::async_read private

2014-01-07 Thread Christophe Fergeau
--- server/reds_stream.c | 26 ++ server/reds_stream.h | 2 -- 2 files changed, 14 insertions(+), 14 deletions(-) diff --git a/server/reds_stream.c b/server/reds_stream.c index d0d8213..837d2cb 100644 --- a/server/reds_stream.c +++ b/server/reds_stream.c @@ -71,6 +71,8 @@

[Spice-devel] [PATCH 05/17] Introduce reds_stream_new() helper

2014-01-07 Thread Christophe Fergeau
Initializing a new stream means initializing quite a few fields. This commit factors this initialization in a dedicated reds_stream_new helper. This also helps moving more code from reds.c to reds_stream.c --- server/reds.c| 22 ++ server/reds_stream.c | 29

[Spice-devel] [PATCH 13/17] Make RedsStream::sasl private

2014-01-07 Thread Christophe Fergeau
--- server/reds_stream.c | 107 ++- server/reds_stream.h | 35 - 2 files changed, 71 insertions(+), 71 deletions(-) diff --git a/server/reds_stream.c b/server/reds_stream.c index 7f6172f..d0d8213 100644 --- a/server/reds_stream.c ++

[Spice-devel] [PATCH 03/17] Move sync_write* to reds_stream.h

2014-01-07 Thread Christophe Fergeau
They are renamed to reds_stream_write* --- server/reds.c| 78 server/reds_stream.c | 28 +++ server/reds_stream.h | 5 3 files changed, 57 insertions(+), 54 deletions(-) diff --git a/server/reds.c b/server/reds.c i

[Spice-devel] [PATCH 08/17] Move SASL authentication to reds_stream.h

2014-01-07 Thread Christophe Fergeau
SASL authentication mostly use members from RedsStream to do its work, so it makes sense to have its code in reds_stream.c. This should allow to make RedsStream::sasl private in the future. --- server/reds.c| 458 - server/reds_stream.c | 510 +++

[Spice-devel] [PATCH 00/17] Split RedsStream out of reds.c

2014-01-07 Thread Christophe Fergeau
Hey, This is a series I've had locally for a while. It moves RedsStream related code out of reds.c to its own file. This shaves ~1000 lines of code out of reds.c The patch series could be split in 2 independent series, first one would be patches 1-8 which is code movements from reds.c to redsstrea

[Spice-devel] [PATCH 10/17] Introduce reds_stream_is_ssl()

2014-01-07 Thread Christophe Fergeau
--- server/inputs_channel.c | 2 +- server/reds.c | 10 +- server/reds_stream.c| 5 + server/reds_stream.h| 1 + 4 files changed, 12 insertions(+), 6 deletions(-) diff --git a/server/inputs_channel.c b/server/inputs_channel.c index 8d4feab..395b81f 100644 --- a/se

[Spice-devel] [PATCH 04/17] reds: Move SSL-related code to RedsStream

2014-01-07 Thread Christophe Fergeau
Code to initiate a SSL stream belongs there --- server/reds.c| 85 +++- server/reds_stream.c | 50 +++ server/reds_stream.h | 2 ++ 3 files changed, 82 insertions(+), 55 deletions(-) diff --git a/server/reds.c b/

[Spice-devel] [PATCH 17/17] Make RedsStream::info private

2014-01-07 Thread Christophe Fergeau
--- server/reds_stream.c | 50 -- server/reds_stream.h | 6 -- 2 files changed, 28 insertions(+), 28 deletions(-) diff --git a/server/reds_stream.c b/server/reds_stream.c index 6af3cd1..331e505 100644 --- a/server/reds_stream.c +++ b/server/red

[Spice-devel] [PATCH 07/17] Move async code to RedsStream

2014-01-07 Thread Christophe Fergeau
The AsyncRead structure in reds.h wraps an async read + callback to be done on a stream. Moving it to reds_stream.h is needed in order to move SASL authentication there. --- server/reds.c| 60 server/reds_stream.c | 64 ++

[Spice-devel] [PATCH 16/17] Introduce reds_stream_set_channel()

2014-01-07 Thread Christophe Fergeau
--- server/reds.c| 6 +++--- server/reds_stream.c | 9 + server/reds_stream.h | 2 ++ 3 files changed, 14 insertions(+), 3 deletions(-) diff --git a/server/reds.c b/server/reds.c index a993f2c..c6983d8 100644 --- a/server/reds.c +++ b/server/reds.c @@ -1416,9 +1416,9 @@ static voi

[Spice-devel] [PATCH 15/17] Introduce reds_stream_set_info_flag()

2014-01-07 Thread Christophe Fergeau
--- server/reds.c| 2 +- server/reds_stream.c | 10 ++ server/reds_stream.h | 1 + 3 files changed, 12 insertions(+), 1 deletion(-) diff --git a/server/reds.c b/server/reds.c index f35f989..a993f2c 100644 --- a/server/reds.c +++ b/server/reds.c @@ -1414,7 +1414,7 @@ static void

[Spice-devel] [PATCH 01/17] Move SPICE_GNUC_VISIBLE to red_common.h

2014-01-07 Thread Christophe Fergeau
--- server/red_common.h | 2 ++ server/reds.h | 2 -- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/server/red_common.h b/server/red_common.h index 585b13c..b6b643a 100644 --- a/server/red_common.h +++ b/server/red_common.h @@ -29,6 +29,8 @@ #include "spice.h" +#define

Re: [Spice-devel] Fw: Re: multiple client connect spice-server

2014-01-07 Thread Lindsay Mathieson
On Tue, 7 Jan 2014 10:38:26 AM David Jaša wrote: > No, only one client can connect at the same time. > > David > > On Út, 2014-01-07 at 10:05 +0800, hhb584520 wrote: > > how to multiple spice clients can connect to spice server at one time? It can be done: http://www.spice-space.org/page/Fea

Re: [Spice-devel] Fw: Re: multiple client connect spice-server

2014-01-07 Thread David Jaša
No, only one client can connect at the same time. David On Út, 2014-01-07 at 10:05 +0800, hhb584520 wrote: > how to multiple spice clients can connect to spice server at one time? > > thank you! > > > > > hhb584520 > > From: Liang Guo > Date: 2014-01-06 23:31 > To: hhb584520 > Subject: Re:

[Spice-devel] Fw: Re: multiple client connect spice-server

2014-01-07 Thread hhb584520
how to multiple spice clients can connect to spice server at one time? thank you! hhb584520 From: Liang Guo Date: 2014-01-06 23:31 To: hhb584520 Subject: Re: multiple client connect spice-server Hi, AFAIK, only one spice client can connect to spice server at one time. You'd better ask this