Re: [tor-dev] Tor Arch Diagrams
On 03/08/2017 02:01 PM, Nick Mathewson wrote: > Thanks, Chelsea! How would you like to get these into the > documentation? I was thinking that adding them to > https://people.torproject.org/~nickm/tor-auto/internal/ > [generated from >https://gitweb.torproject.org/user/nickm/tor-guts.git > ] > might be a good place, but there could be other logical locations too. Yes, sounds like a good place for them. > I'd be glad to integrate them if you like, or collaborate on > explanatory text to go along with them. Collaborating would be great, and we might even get new information out of the process. Thanks, I'll write you to organize. Chelsea ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
Re: [tor-dev] Tor Arch Diagrams
On Mon, Mar 6, 2017 at 11:42 PM, chelsea komlo wrote: > Hello All, > > I've published object diagrams created from a conversation with Nick at > the last Tor meeting, along with the original sketches (hopefully very > similar). > > github.com/chelseakomlo/tor_arch > > The plan for these is to include them into documentation. These should > definitely evolve along with tor's architecture, so please don't think > of them as set in stone. Thanks, Chelsea! How would you like to get these into the documentation? I was thinking that adding them to https://people.torproject.org/~nickm/tor-auto/internal/ [generated from https://gitweb.torproject.org/user/nickm/tor-guts.git ] might be a good place, but there could be other logical locations too. I'd be glad to integrate them if you like, or collaborate on explanatory text to go along with them. cheers, -- Nick ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
[tor-dev] Tor Arch Diagrams
Hello All, I've published object diagrams created from a conversation with Nick at the last Tor meeting, along with the original sketches (hopefully very similar). github.com/chelseakomlo/tor_arch The plan for these is to include them into documentation. These should definitely evolve along with tor's architecture, so please don't think of them as set in stone. A couple questions/comments: - What else should be included? The most important thing is that these are good visual assets for future discussions on topics such as modularization, where code/responsibility should belong, if any new structures are needed, etc. - Some of these may need more information. For example, the scheduler diagram. - If object diagrams do not capture tor's architecture accurately, we can also look at event modeling. This would model what happens as different events occur from start to finish in the tor network. - If it is useful for these to be UML, I can do that. But more importantly is that they are useful. Feedback welcome! Chelsea ___ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
