[tahoe-lafs-trac-stream] [Tahoe-LAFS] #38: state machine diagrams, data flow diagrams

[Tahoe-LAFS]

#38: state machine diagrams, data flow diagrams
-------------------------------+------------------------
     Reporter:  zooko          |      Owner:  somebody
         Type:  enhancement    |     Status:  closed
     Priority:  major          |  Milestone:  eventually
    Component:  documentation  |    Version:  0.6.0
   Resolution:  invalid        |   Keywords:  docs
Launchpad Bug:                 |
-------------------------------+------------------------
Changes (by exarkun):

 * status:  new => closed
 * resolution:   => invalid


Old description:

> {{{
> <faried> i am in a maze of twisty classes
> [13:39]
> <faried> i thought i'd try to figure out the file size problem on my own,
> and
>          yow, it's a lot of digging
> <faried> ah, the filesize is in the uri, second-last component
> [13:56]
> <faried> OSError: [Errno 13] Permission denied:
>          '/home/trac/projects/tahoe/attachments/ticket'
> [14:11]
> <faried> i tried uploading a patch against my ticket (37)
> *** Users on #mnet: zooko MikeW faried SamB cryptomonkey guruz vaste
> <zooko> Too many classes?  Too little documentation?  I'd like to know
> what
>         you think.
> [16:11]
> <zooko> I'm extremely happy with it myself, but maybe I'm missing
> something.
> <zooko> faried: try uploading again?
> [16:13]
> <faried> oh, i figured it out
> [16:18]
> <faried> i darcs send'd you a patch for that
> <faried> and a partial patch for ticket #33
> [16:19]
> <faried> i just didn't realize that the uri had the file size encoded in
> it
> <faried> probably because i didn't read the entire uri; i didn't scroll
> all
>          the way to the right side of the page
> [16:20]
> <zooko> faried: so is there a spot where I could add or improve
> documentation
>         so that the next hacker will figure out whats in a URI more
> easily?
> [16:22]
> <zooko> By the way, thank you very much!
> <zooko> I fixed the perms and attached your patches to trac.
> <faried> i think a little chart like this would help:
> [16:23]
> <faried>
> /download_uri/URI%3Acrs%3A6975-25-100%3A6975-25-100%3Aqjnabbrtceuzbcziuofyzq2f4ecdqnxy%3Afo4pxinuaki6k6fxwxbw5havybzu72br%3Aykctc7jprjbhkwl3anfiwvz55y%3D%3D%3D%3D%3D%3D%3Ac5x6zeht34ok7lhrrhpi74kokprcblzlucza36x7fqque2zi5qya%3D%3D%3D%3D%3A25%3A100%3A6958%3A6975?filename=INTERNALS
> <faried> it's /tmp/INTERNALS in the testing nodes
> <faried> a description of what happens when an event occurs might be
> helpful
> [16:24]
> <faried> something like a stacktrace, maybe
> [16:25]
> <faried> when a user clicks on a download link, this code gets called
> that
>          calls this other code to talk to the introducer that blah blah
> blah
> [16:26]
>
> }}}

New description:

 {{{
 <faried> i am in a maze of twisty classes
 [13:39]
 <faried> i thought i'd try to figure out the file size problem on my own,
 and
          yow, it's a lot of digging
 <faried> ah, the filesize is in the uri, second-last component
 [13:56]
 <faried> OSError: [Errno 13] Permission denied:
          '/home/trac/projects/tahoe/attachments/ticket'
 [14:11]
 <faried> i tried uploading a patch against my ticket (37)
 *** Users on #mnet: zooko MikeW faried SamB cryptomonkey guruz vaste
 <zooko> Too many classes?  Too little documentation?  I'd like to know
 what
         you think.
 [16:11]
 <zooko> I'm extremely happy with it myself, but maybe I'm missing
 something.
 <zooko> faried: try uploading again?
 [16:13]
 <faried> oh, i figured it out
 [16:18]
 <faried> i darcs send'd you a patch for that
 <faried> and a partial patch for ticket #33
 [16:19]
 <faried> i just didn't realize that the uri had the file size encoded in
 it
 <faried> probably because i didn't read the entire uri; i didn't scroll
 all
          the way to the right side of the page
 [16:20]
 <zooko> faried: so is there a spot where I could add or improve
 documentation
         so that the next hacker will figure out whats in a URI more
 easily?
 [16:22]
 <zooko> By the way, thank you very much!
 <zooko> I fixed the perms and attached your patches to trac.
 <faried> i think a little chart like this would help:
 [16:23]
 <faried>
 /download_uri/URI%3Acrs%3A6975-25-100%3A6975-25-100%3Aqjnabbrtceuzbcziuofyzq2f4ecdqnxy%3Afo4pxinuaki6k6fxwxbw5havybzu72br%3Aykctc7jprjbhkwl3anfiwvz55y%3D%3D%3D%3D%3D%3D%3Ac5x6zeht34ok7lhrrhpi74kokprcblzlucza36x7fqque2zi5qya%3D%3D%3D%3D%3A25%3A100%3A6958%3A6975?filename=INTERNALS
 <faried> it's /tmp/INTERNALS in the testing nodes
 <faried> a description of what happens when an event occurs might be
 helpful
 [16:24]
 <faried> something like a stacktrace, maybe
 [16:25]
 <faried> when a user clicks on a download link, this code gets called that
          calls this other code to talk to the introducer that blah blah
 blah
 [16:26]

 }}}

--

Comment:

 There's nothing specific enough here to be actionable for anyone still
 active on the project.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/38#comment:4>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage