[tahoe-lafs-trac-stream] [tahoe-lafs] #1310: If --node-url is present then --node-directory is mostly but not entirely ignored.

[tahoe-lafs]

#1310: If --node-url is present then --node-directory is mostly but not entirely
ignored.
-----------------------------------+----------------------------------------
     Reporter:  zooko              |       Owner:  warner   
         Type:  defect             |      Status:  reopened 
     Priority:  major              |   Milestone:  undecided
    Component:  code-frontend-cli  |     Version:  1.8.1    
   Resolution:                     |    Keywords:  usability
Launchpad Bug:                     |  
-----------------------------------+----------------------------------------

Comment (by zooko):

 I still have the feeling that tahoe-lafs gateways and tahoe-lafs clients
 are separate objects (for example, I prefer to run my gateways and my
 clients under separate user accounts on the same machine sometimes), and
 they should not share state in this way. I find it confusing.

 Replying to [comment:6 warner]:
 > I've gotta run, I'll come back to this ticket later to chime in about
 > the proposal. At first glance, {{{--cli-directory}}} does sound more
 > accurate, but I think the parallelism of {{{--node-directory}}}
 > everywhere is valuable.

 I have the feeling that this is really wrong -- that you shouldn't say
 {{{--node-directory}}} to a gateway to mean the directory where it stores
 its persistent state such as the {{{node.pem}}} and also say {{{--node-
 directory}}} to a client to mean the directory where it stores its
 persistent state such as the {{{backupdb.sqlite}}}. It is the "bad" kind
 of parallelism, when the underlying thing is different, so the interface
 to it ''ought'' to be different too. :-)

 (Also, I think it would help us all think and communicate more precisely
 if we stopped using the ambiguous word "node"... Except in those cases
 where we actually mean a Tahoe-LAFS process which runs more than one of
 (server, gateway, introducer) or which runs an unspecified service.)

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1310#comment:7>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage