From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 51CD2791EB for ; Fri, 1 Jan 2016 11:10:41 -0800 (PST) Received: from resomta-ch2-14v.sys.comcast.net ([69.252.207.110]) by resqmta-ch2-08v.sys.comcast.net with comcast id 0jA71s0032PT3Qt01jBCuL; Fri, 01 Jan 2016 19:11:12 +0000 Received: from eklhad ([IPv6:2601:405:4001:e487:21e:4fff:fec2:a0f1]) by resomta-ch2-14v.sys.comcast.net with comcast id 0jBB1s0042MDcd701jBBpJ; Fri, 01 Jan 2016 19:11:11 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke Reply-to: Karl Dahlke References: <20151130125742.eklhad@comcast.net> <20160101185027.GC12402@122oven.adamthompson.me.uk> User-Agent: edbrowse/3.6.0+ Date: Fri, 01 Jan 2016 14:11:11 -0500 Message-ID: <20160001141111.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1451675472; bh=8U8o74y6LINhmXaGA0cP/J48dhQ1kS5CMAyN+xddSic=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=u4bBwyjIxLGPzaN4WYYew9+XvtZ09jBYarh64TBHAQNC7Sp5J8CLVC9KRIqZfeYn3 yUNcc9C+uJfBlcA1Mlb+UB8EQc1mrwloiatpNXW1v8/vQLC1SO4AIuX5aq6e3fQ+NQ Rtt7FPrsmo3zVwhdpWf8AJ4RFIQ2Sqq+U3UlI+7HyDKAfUA5Ml7aTQZhv+KaCzea+C DTVIRWGUCtAhE3OnbsoQFL3d38WfaQhEwRNOQH2MMwPX/u5/hTZdtw288pKxPgMnXc KwROxQxK2YMs1dMConnz336UuiDPIbDxpniuMv4o3u8T5AzG01fT+EXZSwJLV/Ol+w p+fvm/xQnQ0Ug== Subject: [Edbrowse-dev] Ports X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.20 Precedence: list List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Jan 2016 19:10:41 -0000 > Ok, I'd feel slightly better about this if there was a way to make the port > selection automatic rather than configured, > it feels like multi-user would break in exciting ways otherwise. Oops, you're right. I had the model of one edbrowse-curl daemon serving all, and then sure it could listen on the edbrowse-curl port, whatever that is, and all good, but if we spin up one curl server per user, it has to listen on a per-user edbrowse port, so that's a bit more complicated. We'll give this more thought / discussion. Karl Dahlke