From d00cf7daab0706271437394cb93ed739ef75a950 Mon Sep 17 00:00:00 2001 From: zancas Date: Sat, 31 Mar 2012 12:59:47 -0700 Subject: [PATCH] A few minor edits, mostly practicing with git. --- doc/using-foolscap.xhtml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/using-foolscap.xhtml b/doc/using-foolscap.xhtml index 583b70e2..1dbd5853 100644 --- a/doc/using-foolscap.xhtml +++ b/doc/using-foolscap.xhtml @@ -60,7 +60,7 @@ subclass Referenceable. Let's create a simple server which does basic arithmetic. You might use such a service to perform difficult mathematical operations, like addition, on a remote machine which -is faster and more capable than your ownalthough +is faster and more capable than your own although really, if your client machine is too slow to perform this kind of math, it is probably too slow to run python or use a network, so you should seriously consider a hardware upgrade.

@@ -141,10 +141,10 @@ kind of problem.

To make any of your Referenceables available, you must make your Tub available. There are three parts: give it an identity, have it listen on a port, and tell it the protocol/hostname/portnumber at which that -port is accessibly to the outside world.

+port is accessible to the outside world.

In general, the Tub will generate its own identity, the TubID, by -creating an SSL public key certificate and hashing it into a suitably-long +creating a self-signed SSL public key certificate and hashing it into a suitably-long random-looking string. This is the primary identifier of the Tub: everything else is just a location hint that suggests how the Tub might be reached. The fact that the TubID is tied to the public key allows FURLs to