This document also discusses farBook exposure to users and how to control
far://<ip_address|URL>:<port_number>/<farBook_name>For example, if you have an farBook named myBook on your home machine, which has an ip address of 184.108.40.206 and you have set farVIEW running on your home machine to listen on port 5280, you would enter the link into the Source property as
far://220.127.116.11:5280/myBookThere is no default for any field. Note that if the host computer has a URL, you can use that in place of the ip address.
To use the link while browsing, open the link to the remote farBook by opening the linking topic in the usual way, i.e., by clicking on the topic's icon with the left mouse button. That causes your local farVIEW to connect to the remote farVIEW host, which opens the topic to display the contents of the remote farBook. You browse the contents representing the remote farBook in the normal manner. Note that you will probably experience a slower response from farVIEW than you are normally accustomed when accessing a remote farBook so be patient. When you close the link topic, you close the connection between your local farVIEW and the remote farVIEW.
As I mentioned, you can also use a "far-link" from the command line,
but in that case, you will only access the remote farBook, not a local
|Note that there must be exactly three slashes.|
Use this form to link from a remote farBook to another farBook on the same host machine. Your local farVIEW will automatically resolve a local link in a remote farBook to link to the intended remote farBook. If the remote farBook contains a remote far-link to a third machine, your farVIEW guest will connect to the second host machine just as it did to the first host machine.
farVIEW does not yet support remote farBook topics that represent data
files on the remote machine. If you have a topic in the remote farBook
that identifies, say, a Word document on the host machine, farVIEW does
not currently localize the file for you on your local machine. But that
ability is required of farVIEW, and I plan to implement it soon. For now,
during this early test phase, you are restricted to using the built in
editor with text that is within the remote farBook.
[Comm]Set the [Books] section to show which farBook(s) you want to be visible via the listen port (5280
accept=link | body
listenPort=5280 ; set this to a non-zero number
serverIP=10.15.3.33 ; not yet used
serverPort=8000 ; not yet used
userName=<your user name here> ; set this to your chosen farVIEW name
[Books]The example exposes two farBooks: farview and myBook. Note that the value associated with the farBook name is the path, either the relative path from the working directory that you specify in your farVIEW shortcut on the host (as in the first example), or the absolute path (as in the second example).
farview=farview.vue ; in the default folder
myBook=c:\my book folder\mybook.vue
sizes=100,100,60,40,20,10,5,1 ; %extra space
Note that, assuming that the host PC has an ip address of 18.104.22.168, the far-links for these two farBooks are
far://22.214.171.124:5280/myBookIf the entries that provide the location information for the farBooks is not in the [Books] section, these far-links will fail.
You can determine the ip address assigned to the host PC by running
the Microsoft program ipconfig in a MSDOS window on the host.
[myBook]The key-list is optional. If you aren't using it, just use the word user. It has no special significance, it will just help you remember to include the equal-sign, which is absolutely required to allow the user to have access to the farBook; in this case, myBook. I'll explain the key-list in the following section about locks and keys..
jeRaven = [<key-list>]
drTurbo = [<key-list>]
* = [<key-list>]
For the following discussion, suppose you have decided to identify your personnel as belonging to one or more of the following groups:
Note that if a topic is anonymous, i.e., if the Owner field in its Property dialog is empty or not present, then the topic is not owned, and its exposure level won't matter, that topic is always public.
Because the basic farVIEW visual interface is through the Contents window, which is a tree structure, a topic that is the parent of a set of children topics controls the user's access to those children. Thus, the exposure of the farVIEW root topic determines the exposure of its children, and each of those child topics control the exposure of their children in a top-down sort of way.
I should note that the owner of a topic always has full access to that topic, assuming that the path from the root topic to the topic in question is unencumbered by restricting locks..
For example, if you want to allow the administrative and executive staff to make changes to a topic, and allow the marketing staff to examine it but not change it, you would enter the following into the Exposure field:
public(admin,exec) browse(mkt)Note that this specification rejects any user who is not in one of the two groups.
You code the key-list for jeraven as follows:
[MyBook]jeraven has browse access to the topic while drturbo has public (edit) access to the topic.
jeRaven = fin, mkt
drTurbo = exec, eng