<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/arti-client/src/err.rs, branch arti-v0.0.2</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.2</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.0.2'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2021-11-21T15:54:34Z</updated>
<entry>
<title>Make arti-client config object match arti config better.</title>
<updated>2021-11-21T15:54:34Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-11-19T07:11:17Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=0372d24eedbef7541e12ea046abad9b33749ac4b'/>
<id>urn:sha1:0372d24eedbef7541e12ea046abad9b33749ac4b</id>
<content type='text'>
Now every section that the two configuration objects share has the
same type and name.  This should help us in documenting our configuration
in a way that doesn't confuse people.

There is still lots of API work to go.
</content>
</entry>
<entry>
<title>Improve top-level arti-client documentation, add example code</title>
<updated>2021-10-28T18:20:42Z</updated>
<author>
<name>eta</name>
<email>tor@eta.st</email>
</author>
<published>2021-10-28T17:32:49Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=dcdd8c59dfa6afd3ee903d5eacab4a99c1258e7d'/>
<id>urn:sha1:dcdd8c59dfa6afd3ee903d5eacab4a99c1258e7d</id>
<content type='text'>
This overhauls the top-level `arti-client` documentation significantly:

- the "Using arti-client" section walks the user through all of the
  necessary steps to initiate a Torified TCP connection, and then
  provides a code example
  - this example is also available as `examples/readme.rs`; it's not run
    as a doctest, since it involves connecting to Tor
  - a "More advanced usage" subheading provides information about stream
    isolation (and can potentially be used for other interesting
    features once we get them).
- a new "Multiple runtime support" section was added to explain the
  purpose and usage of the `tor-rtcompat` crate
- the section on design and privacy considerations was removed; this is
  probably okay to keep in a README, but users of the crate aren't going
  to be interested in this (at least I don't think)

(also, the doc comment for `arti_client::Error` was fixed to make actual
sense)
</content>
</entry>
<entry>
<title>TorClient::resolve_ptr should take an IpAddr.</title>
<updated>2021-10-26T13:42:25Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-10-26T13:42:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=be4823818e191d871325a4334966801c562f36bd'/>
<id>urn:sha1:be4823818e191d871325a4334966801c562f36bd</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rename tor_client/arti_tor_client to arti_client.</title>
<updated>2021-10-21T18:22:11Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2021-10-21T18:15:13Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7c7a388e287afa0e168d8d666da6649a5750b9b5'/>
<id>urn:sha1:7c7a388e287afa0e168d8d666da6649a5750b9b5</id>
<content type='text'>
Solves a name conflict with the existing tor_client create.

Closes #130.
</content>
</entry>
</feed>
