Re: Window Scale option

[[e-mail]]

  *> 
  *> I guess what I'm really saying is that if you have a user interface
  *> to TCP to allow the application to specify the window scale value
  *> without having to set the buffer size,

Dave,

Why would you want to do that?  It seems to me that the window scale
itself should be *completely* hidden from the application; it is after
all a kludge; as you noted earlier, we want to obsolete it eventually
with a sensible window size.  The application should know ONLY about
buffer sizes!

  *> and the server turns around
  *> the window scale value, then you can make TCP connections that are
  *> ready to use large buffers if the application wants them, without
  *> having to pre-allocate any extra buffer space on either the client
  *> or the server (and thus have an initial large window).  But typically

Oh, you mean that there could be a system call that set the buffer max,
without pre-allocation of buffers.  But since it has to be ABLE to
allocate that buffer space, you can still lose at the beginning.

  *> the client will know whether or not large buffers are wanted, so
  *> having it set a large receive buffer, and having the server turn around
  *> the scale option (without changing the buffer size) is usually sufficient.
  *> 

Bob