From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.134.218 with SMTP id k26cs29895bkt; Fri, 4 Jun 2010 20:58:34 -0700 (PDT) Received: by 10.231.59.80 with SMTP id k16mr1784220ibh.114.1275710313279; Fri, 04 Jun 2010 20:58:33 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id c18si3174538ibi.87.2010.06.04.20.58.32; Fri, 04 Jun 2010 20:58:33 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 96E9B3C8050; Fri, 4 Jun 2010 23:58:32 -0400 (EDT) Received: from pion.club.cc.cmu.edu (PION.CLUB.CC.CMU.EDU [128.237.157.88]) by rubyforge.org (Postfix) with ESMTP id 93D03185835A for ; Fri, 4 Jun 2010 23:55:04 -0400 (EDT) Received: from rlane by pion.club.cc.cmu.edu with local (Exim 4.69) (envelope-from ) id 1OKkTP-0007fu-Pl; Fri, 04 Jun 2010 23:55:03 -0400 From: Rich Lane To: Jason Petsod In-reply-to: <1275666025-sup-4912@acheron.quadco.net> References: <1272606137-sup-842@acheron.quadco.net> <1272644331-sup-1274@zyrg.net> <1275577785-sup-679@zyrg.net> <1275666025-sup-4912@acheron.quadco.net> Date: Fri, 04 Jun 2010 23:55:03 -0400 Message-Id: <1275706760-sup-1122@zyrg.net> User-Agent: Sup/git Cc: sup-talk Subject: Re: [sup-talk] sup web interface X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from Jason Petsod's message of 2010-06-04 11:59:15 -0400: > For threading, I had to add a new command 'thread' to sup-server, so you'll > need to apply a patch [2] before it works. I've applied this to master. However, I think the final protocol support for threading is going to be more complicated. Right now in the best case this is going to result in a request for every thread displayed, and in the worst case where thread requests are pipelined we could have a lot of redundant message responses. The best I've come up with is adding a "thread" option to query that mimics ThreadSet#load_n_threads. > Also, it's not evident to me that the sup-server polls for new messages or > has the ability to add new messages to the index, so checking for new > messages or sending emails doesn't work yet. That functionality shouldn't > hard to add though. Yeah, I need to add a timer to periodically poll the sources. But it should be possible to use the add request already to add sent messages to the index. I took a quick look at sup-web. I think it would be a good idea to spawn an EM reactor thread when the webapp starts (if the server isnt already using one) instead of starting one per sup protocol request. Similarly, you'll probably want to keep a connection pool instead of opening a new connection per sup protocol request. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk