F21 Self Contained Change: Remote Journal Logging

Miloslav Trmač mitr at volny.cz
Tue Apr 22 18:58:37 UTC 2014

2014-04-22 20:19 GMT+02:00 Simo Sorce <simo at redhat.com>:

> On Tue, 2014-04-22 at 19:04 +0200, Miloslav Trmač wrote:
> > 2014-04-22 15:10 GMT+02:00 Simo Sorce <simo at redhat.com>:
> >
> > > A good protocol would allow to send a first small
> > > packet that establish a connection and a reply that can "push back" on
> > > the client w/o requiring huge bandwidth to be spent.
> > >
> >
> > Isn't that an inherent capability of TCP?
> Sure, that's one way when bandwidth is the issue. There are other issues
> though, and just closing the connection on the client if you do not want
> any traffic is a bit blunt. It also does not give the client any idea
> when it is ok to retry.

Not like that—just stop reading from the socket, causing the server to
advertise a zero-length window to the client.  The client will then know
that writes are blocking / not being processed.  And when the server has
more capacity, free up the buffers and the kernel will send a window update
to the client automatically.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20140422/ae52edc2/attachment.html>

More information about the devel mailing list