79 | | Foolscap is not yet ready for production use. The [source:doc/todo.txt |
80 | | 'todo.txt'] and [source:doc/jobs.txt 'jobs.txt'] files contain some of the |
81 | | things that need finishing before it will be ready. Connection negotiation |
82 | | needs to be changed to use variable-length certificate digests and |
83 | | certificate chains and variable-length object names, various questions about |
84 | | making objects "giftable" by default or not need to be answered and |
85 | | implemented, and we need to acquire operational experience with Foolscap as a |
86 | | whole to think about usability. |
| 79 | Foolscap is slowly getting closer to being ready for production use. |
| 80 | Applications which have full control over both ends of the wire and which can |
| 81 | thus tolerate wire-protocol changes are probably the best candidate. |
88 | | Release 0.1.7 (as well as older releases) are available in the [/releases/ |
| 83 | The [source:doc/todo.txt 'todo.txt'] and [source:doc/jobs.txt 'jobs.txt'] |
| 84 | files contain some of the things that need finishing before it will be ready. |
| 85 | Connection negotiation needs to be changed to use variable-length certificate |
| 86 | digests and certificate chains and variable-length object names, various |
| 87 | questions about making objects "giftable" by default or not need to be |
| 88 | answered and implemented, and we need to acquire operational experience with |
| 89 | Foolscap as a whole to think about usability. |
| 90 | |
| 91 | Release 0.2.0 (as well as older releases) are available in the [/releases/ |