Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750987AbVJXNEc (ORCPT ); Mon, 24 Oct 2005 09:04:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750988AbVJXNEc (ORCPT ); Mon, 24 Oct 2005 09:04:32 -0400 Received: from sp-260-1.net4.netcentrix.net ([4.21.254.118]:13576 "EHLO asmodeus.mcnaught.org") by vger.kernel.org with ESMTP id S1750982AbVJXNEc (ORCPT ); Mon, 24 Oct 2005 09:04:32 -0400 To: "Travis H." Cc: linux-kernel@vger.kernel.org Subject: Re: terminal handling: collecting inter-keystroke timings References: From: Douglas McNaught Date: Mon, 24 Oct 2005 09:01:46 -0400 In-Reply-To: (Travis H.'s message of "Mon, 24 Oct 2005 02:46:07 -0500") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (darwin) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1009 Lines: 26 "Travis H." writes: > I'd like to be able to do it with (ttys attached to?) network sockets > as well, so that I could test out the applicability of it to remote > users. One issue here is Nagle--you'll definitely want to turn that off, and I don't think you can do it from the server side. Also, I think SSH does its own batching of keystrokes, to decrease the overhead of the crypto encapsulation. So this part seems like a hard problem without a cooperating client. > > Ideally any mechanism would be flexible enough that I could have it > deliver me timings between key-down, key-up-to-key-down, or up/down to > up/down timings. You're not going to be able to do that with network connections, only locally attached keyboards. -Doug - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/