AMIGIFT Documentation

Browsing /Maintenance



Remember that most peer-to-peer networks are not perfect and may often need a little nudge from users to keep them operational. Specifically, you need to make sure the protocol plugins have the necessary caches of nodes which they will use to make their initial entry into the network. If this file is largely out of date (especially if you haven't used AMIGIFT in a while) then it is likely you will not be able to find a new node to connect to and thus it will seem that AMIGIFT is doing "nothing".

To correct this problem you may need to examine the contents of your AMIGIFT:daemon/{plugin} directories and replace the nodes or cache files that are appropriate. For example, you can replace OpenFT's local nodes cache with the global default provided by us by simply removing the AMIGIFT:daemon/OpenFT/nodes and starting the daemon (do not remove while it is running). This may or may not provide a higher quality nodes file depending on the age of your OpenFT version and other factors..

"Protocol X cannot connect, what's wrong?" is certainly the most frequent (and most annoying) question that we receive, so I'm going to force all you to choke on a little background information before I even attempt an answer.

First, it is important to understand that giftd provides a framework for third-party plugins in which to nest, but it does not actually control how those plugins work, or develop. For this reason, the upstream AMIGIFT developers often have no idea why some unknown/foreign protocol plugin is not working exactly as you might expect. Naturally, you should contact the appropriate development team when attempting to request support...

Second, a common property of most peer-to-peer networks is the extremely limited availability of peers and peer resources. This often means that new users will be devalued and may require additional time to connect, or may not even be able to connect at all when the most localized group of nodes is unable to accept connections. This is especially true with smaller networks like OpenFT which do not have a large probabilistic network to poll from when certain sections become stressed. Yes, it sucks, we know this. The few things we can do to improve the situation are constantly being explored and worked on, but as is a common theme with most open source projects, we simply don't have the time to do everything!

And now finally the answer... Each protocol plugin has its own method of node discovery and propagation (as do most networks, independent of their giFT-API implementations), which means that there is no one unified answer to this question. For OpenFT you can often find a more up-to-date nodes file to replace the default by using the GiFTMui's tools menu, or starting with Version 2.0 you can use the new online updater facility. Please note that this method does not guarantee a network connection! You should consult the appropriate network plugin documentation (if any exists) and find the answer in the context of that plugin.




Getting Started
go to index
Development




 $Id: index.php,v 2.0 2009/08/06 22:47:32 diegocr Exp $