From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: process.c: read_process_output: hard coded 4096 bytes read limit Date: Wed, 26 Jun 2013 09:16:13 -0400 Message-ID: References: <87txkpjhvd.fsf@igel.home> <87sj059j9o.fsf@zigzag.favinet> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1372252586 4607 80.91.229.3 (26 Jun 2013 13:16:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 26 Jun 2013 13:16:26 +0000 (UTC) Cc: Miguel Guedes , emacs-devel@gnu.org To: Thien-Thi Nguyen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 26 15:16:26 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UrpaD-0003gp-CA for ged-emacs-devel@m.gmane.org; Wed, 26 Jun 2013 15:16:25 +0200 Original-Received: from localhost ([::1]:47230 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UrpaC-0006e0-M6 for ged-emacs-devel@m.gmane.org; Wed, 26 Jun 2013 09:16:24 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52922) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Urpa5-0006dd-3J for emacs-devel@gnu.org; Wed, 26 Jun 2013 09:16:22 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Urpa3-0001Cw-5m for emacs-devel@gnu.org; Wed, 26 Jun 2013 09:16:16 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:44366) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Urpa3-0001C9-16; Wed, 26 Jun 2013 09:16:15 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av4EABK/CFFMCppA/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLNBIUGA0kiB4GwS2NGoNwA5IgjTyFHoFegxOBSw X-IPAS-Result: Av4EABK/CFFMCppA/2dsb2JhbABEvw4Xc4IeAQEEAVYjBQsLNBIUGA0kiB4GwS2NGoNwA5IgjTyFHoFegxOBSw X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="17200452" Original-Received: from 76-10-154-64.dsl.teksavvy.com (HELO pastel.home) ([76.10.154.64]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 26 Jun 2013 09:16:08 -0400 Original-Received: by pastel.home (Postfix, from userid 20848) id AAFF562E11; Wed, 26 Jun 2013 09:16:13 -0400 (EDT) In-Reply-To: <87sj059j9o.fsf@zigzag.favinet> (Thien-Thi Nguyen's message of "Wed, 26 Jun 2013 13:57:39 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:161092 Archived-At: > How would you use accept-process-output with an asynchronous process > channel? E.g. when would you call it? How do you know when there is > data available? > Presumably the protocol specifies a format for the received data that > includes some kind of "end of message" marker. You know there is data > available when that marker is not present (given a well-formed message). > For example: But accept-process-output is synchronous: while running it, nothing else can happen. It's important to make sure that the performance is good enough with accept-process-output but it should *also* be good enough without accept-process-output. Stefan