IINM, TCP_NODELAY on setsockopt isn't a "don't make this socket needlessly slow" option. I believe it's a "kernel, I know someone was using this port recently, but please let me listen on it right away anyway" option.
If you're seeing lag, I'd guess either your network is laggy, or lsh just has some algorithm choices that could be reevaluated, or too deep nesting of functions or something like that. On Thu, 2003-08-07 at 10:51, Pete Naylor wrote: > I'm noticing that lsh seems terribly laggy when used for an interactive > shell. Looking at the source I don't see the TCP_NODELAY socket option > set anywhere. Perhaps this could be added (possibly only for an > interactive shell if that can be determined) ? > > I did try to add it to the setsockopt call in io.c myself to see if it'd > help, but for whatever reason it doesn't want to build after I make any > edits - something to do with the abstraction stuff I guess. -- Dan Stromberg DCS/NACS/UCI <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
