Intentional Naming System/Twine

This document contains a brief overview of how to run Twine, the new version of INS. It may be helpful to read the documentation for the original version of INS, as most of the functionality has been carried over to Twine.

It is also very useful to take a look at the ins/scripts directory. It contains several scripts useful to understand how to use INS/Twine.

Main features

Twine supports most of the original INS API, but implements a very different kind of resolver.

Running a Twine Resolver

A sample ping.stations file looks like this:

first.ping.station.net 20001
second.ping.station.net 20001
third.ping.station.net 20001
...

Sample Applications

Several sample applications are located in ins.apps. Most of them are described here.

ins.apps.tests.TwineTester is the main test application for Twine resolvers. It is almost identical to ins.api.AppTests, but it uses some features particular to Twine. For example it doesn't use vspaces. This application is intented for experimentation.

ins.apps.tests.SearchCFS is an application developed for searching in CFS. In fact it's a very useful application to run experiments. It has an interface very similar to TwineTester, but it takes very different commands on the interactive prompt.

Developing New Applications

To develop a client application for Twine, proceed as follows:

Troubleshooting

For further information contact:
Magdalena Balazinska
mbalazin@lcs.mit.edu