Difference between revisions of "Borgification"
(standards) |
(API examples) |
||
| Line 5: | Line 5: | ||
A major aspect of borgification is the unification of external resources with the time domain (linear and cycles). This gives history, scheduling, analysis and budgeting to the resources and allows them to be incorporated into the network so that they can be managed by the network or using the [[peer]] interface. | A major aspect of borgification is the unification of external resources with the time domain (linear and cycles). This gives history, scheduling, analysis and budgeting to the resources and allows them to be incorporated into the network so that they can be managed by the network or using the [[peer]] interface. | ||
| − | The network connects with the foreign services on behalf of the network users, as far as they're concerned they don't leave their own local peer environment, so they can change the way it looks and works just like anything else. This allows the network to act as a load-balancing and distributed backup solution for the external service without the service having to change anything. The service or organisation being used in this way could also support the process and make it more efficient still, for instance by offering an [[Wikipedia:API|API]]. | + | The network connects with the foreign services on behalf of the network users, as far as they're concerned they don't leave their own local peer environment, so they can change the way it looks and works just like anything else. This allows the network to act as a load-balancing and distributed backup solution for the external service without the service having to change anything. The service or organisation being used in this way could also support the process and make it more efficient still, for instance by offering an [[Wikipedia:API|API]]. Some services already offer this, such as [http://flickr.com/|flickr] or [http://maps.google.com/|Google maps]. |
These features make it extremely easy to test out the network because it can be used alongside an existing solution and used as much or as little as desired without any concerns about migration. | These features make it extremely easy to test out the network because it can be used alongside an existing solution and used as much or as little as desired without any concerns about migration. | ||
Revision as of 22:26, 12 September 2006
Borgification is the assimilation of established external resources and organisational aspects into the network's holistic system of organisation. It extends the unified network into other foreign "legacy" informational environments such as operating systems, language environments, document repositories, applications and organisations.
Method
A major aspect of borgification is the unification of external resources with the time domain (linear and cycles). This gives history, scheduling, analysis and budgeting to the resources and allows them to be incorporated into the network so that they can be managed by the network or using the peer interface.
The network connects with the foreign services on behalf of the network users, as far as they're concerned they don't leave their own local peer environment, so they can change the way it looks and works just like anything else. This allows the network to act as a load-balancing and distributed backup solution for the external service without the service having to change anything. The service or organisation being used in this way could also support the process and make it more efficient still, for instance by offering an API. Some services already offer this, such as [1] or maps.
These features make it extremely easy to test out the network because it can be used alongside an existing solution and used as much or as little as desired without any concerns about migration.
Borgifying Standards
This is the process of maintaining a class-instance relationship between a nodal context which specific implimentation, or instance of an external standard (the class) such as POSIX. This is similar to the way that the GNU Unix-like components maintain their conformance to the POSIX standard
Applications
- Pricespy style "scrapers"
- Bank statement retrieval and parsing and transfers etc
- Remote installation/upgrading over SSH or between peerd's
- Network monitoring and analysis
- Wikipedia and other wiki's (incl. other wiki-engines too)
- Borgifying dependencies - project integration with SVN-like env's (some project's are gcc, linux kernel, SDL etc, see also Self Containment)
- Multi OS/lang/hardware support (eg. iPod, XBox)
