FAQ
From Friend2Friend Wiki
If you've got a question not on the list... Please add it!
Contents |
Is there a Demo?
Yes, there is a demo of the XML-VM here.
Technically, What is F2F?
An XML-networking platform of some kind.
Does this project actually work :-)?
No. Well, it depends what you mean. It is a functioning XML virtual machine and implements the behaviour described in the F2F Presentations. However, it could currently be more accurately abbreviated 'F' as in Friend2Friend without the '2', since the comms layer is unspecified. As such it is suitable for grafting on to other systems.
How Do F2F servers communicate?
See above.
Is there a Demo?
Yes, there is a demo of the XML-VM here.
Is it Object Oriented? If so, how?
The PHP class hierarchy is as follows:
| Manages communications, soft-systems | |
| Independent trees of soft-nodes, with their own private key | |
| Unit of resource provision (c.f. software) hosts processes and threads | |
| Optional structure to facilitate thread decentralised communication |
| Set of requests with common origin and uid | |
| Individual operations, usually services |
How will F2F servers communicate?
It's easiest if you have a fixed IP. If you're allocated a dynamic IP, or are behind a firewall, your friends will not be able to contact you directly. In this case, the comms module will help you get in touch, since it pings your friends for incoming traffic. If they have a fixed IP, then the problem is solved.
If both you and your friend cannot be contacted directly, then you will have to contact using an F2F tracker with a fixed IP. This is the F2F equivalent of a mailserver.
How is it different from instant messaging?
IM, like Email, are only about moving data between 2 parties. There is, by design, no mechanism to automate communication any further (e.g. to friends of friends). F2F has an XML scripting language for exactly this purpose.
