[tahoe-lafs-trac-stream] [tahoe-lafs] #1136: don't run a web-API frontend if you don't need one

tahoe-lafs trac at tahoe-lafs.org
Sat Sep 14 17:40:04 UTC 2013


#1136: don't run a web-API frontend if you don't need one
-----------------------------------+-----------------------------
     Reporter:  zooko              |      Owner:  somebody
         Type:  enhancement        |     Status:  new
     Priority:  major              |  Milestone:  eventually
    Component:  code-frontend-web  |    Version:  1.7.1
   Resolution:                     |   Keywords:  security websec
Launchpad Bug:                     |
-----------------------------------+-----------------------------
Changes (by zooko):

 * keywords:  security => security websec


Old description:

> http://tahoe-lafs.org/pipermail/tahoe-dev/2010-June/004457.html
>
> In which Brian wrote:
>
>  Actually, it should be controlled by a tahoe.cfg knob, which defaults to
> True unless you've really created a server-only node. When we get a
> "backup service" or "repair service" implemented, in which
> uploads/repairs/whatever are being driven by python code inside the Tahoe
> node (perhaps coming from some yet-to-be-invented plugin system), we will
> want client functionality despite no external frontend interfaces being
> active.
>
>  And many "server-only" nodes will eventually want to do client-like
> things, for server-driven repair or rebalancing.

New description:

 http://tahoe-lafs.org/pipermail/tahoe-dev/2010-June/004457.html

 In which Brian wrote:

  Actually, it should be controlled by a tahoe.cfg knob, which defaults to
 True unless you've really created a server-only node. When we get a
 "backup service" or "repair service" implemented, in which
 uploads/repairs/whatever are being driven by python code inside the Tahoe
 node (perhaps coming from some yet-to-be-invented plugin system), we will
 want client functionality despite no external frontend interfaces being
 active.

  And many "server-only" nodes will eventually want to do client-like
 things, for server-driven repair or rebalancing.

--

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1136#comment:3>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage


More information about the tahoe-lafs-trac-stream mailing list