From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6680 invoked by alias); 7 May 2006 21:41:02 -0000 Received: (qmail 6665 invoked by uid 22791); 7 May 2006 21:41:01 -0000 X-Spam-Check-By: sourceware.org Received: from bay111-f5.bay111.hotmail.com (HELO hotmail.com) (64.4.17.15) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 07 May 2006 21:40:59 +0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 7 May 2006 14:40:57 -0700 Message-ID: Received: from 64.4.17.200 by by111fd.bay111.hotmail.msn.com with HTTP; Sun, 07 May 2006 21:40:54 GMT X-Sender: bviksoe@hotmail.com From: "Bjarke Viksoe" To: gdb@sourceware.org Bcc: Subject: Re: asynchronous MI output commands Date: Sun, 07 May 2006 22:30:00 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00068.txt.bz2 >Daniel Jacobowitz wrote: > >If I were writing a front-end, I would have an arbitration layer which >sent questions to GDB and received answers. The answers will come back >one at a time, in the same order the questions were asked. If you send >two -var-evaluate-expression commands, you'll get back two answers, in >that same order. > >Am I missing something? Is there a reason that this isn't enough? No, the abstraction layer is exactly my design - but as I explained: the goal of my tool is that it's used over a remote line (eg. SSH over internet) where the answer can be a couple of 100ms delayed. It is most desirable to be able to send multiple commands and have the front-end digest the answer as they slowly arrive - updating the UI in increments. Yes, my views need to send multiple -var-evaluate-expression and this is the reason that I'm forced to restrict the design to what you describe. The reason it's not good enough: it so slow. Because of the latency, my "abstraction layer" runs in its own thread. This makes the UI wonderfully responsive, but doesn’t allow a component/view to submit a command and read the answer in the same context. Answers arrive out of context and are processed separately - creating a high need to know what the answer originated from. bjarke BVRDE - bvrde.sourceforge.net