On 04/19/2012 02:58 PM, Marc-André Lureau wrote:
On Thu, Apr 19, 2012 at 9:30 AM, Yonit Halperinyhalp...@redhat.com wrote:
The latency factor is in my TODO (see cover letter).
I use ioctl(socket, TIOCOUTQ) in order to find how many bytes are pending in
the tcp snd buffer, in addition to the
On Sun, Apr 22, 2012 at 10:39 AM, Yonit Halperin yhalp...@redhat.com wrote:
A top with N bytes sent
This is the simpler mechanism I have in mind: the client receives a
start mark knowing N bytes are following that were sent directly (in
burst). Once the N bytes are received the client can
On 04/22/2012 04:23 PM, Marc-André Lureau wrote:
On Sun, Apr 22, 2012 at 10:39 AM, Yonit Halperinyhalp...@redhat.com wrote:
A top with N bytes sent
This is the simpler mechanism I have in mind: the client receives a
start mark knowing N bytes are following that were sent directly (in
On 04/18/2012 08:47 PM, Marc-André Lureau wrote:
Hi
On Wed, Apr 18, 2012 at 7:34 PM, Marc-André Lureau
marcandre.lur...@gmail.com wrote:
It would be
- QOS_QUERY(nbytes)
- nbytes of various messages 1 or n
- QOS_ACK
Further questions about this, how can the server really determine the
Marc-André Lureau píše v St 18. 04. 2012 v 19:47 +0200:
Hi
On Wed, Apr 18, 2012 at 7:34 PM, Marc-André Lureau
marcandre.lur...@gmail.com wrote:
It would be
- QOS_QUERY(nbytes)
- nbytes of various messages 1 or n
- QOS_ACK
Further questions about this, how can the server really
If the client's channel has SPICE_COMMON_CAP_QOS_QUERY,
the server's channel can send SPICE_MSG_QOS_QUERY to the client.
In response, the client is expected to send back SPICE_MSG_QOS_ACK
immediately after it receives the message following the query, and
before handling this message. The server
