icecondor
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
icecondor [2008/09/29 03:14] – 192.168.0.2 | icecondor [2008/12/28 20:27] – 71.237.252.103 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | IceCondor: Open Source Location Broker | + | ===== IceCondor: Open Source Location Broker |
+ | See http:// | ||
See [[icecondor: | See [[icecondor: | ||
See [[icecondor: | See [[icecondor: | ||
See [[icecondor: | See [[icecondor: | ||
- | See [[icecondor: | + | See [[icecondor: |
+ | See [[icecondor: | ||
+ | See server [[icecondor: | ||
+ | See [[icecondor: | ||
+ | See [[icecondor: | ||
+ | See [[icecondor: | ||
+ | See [[icecondor: | ||
+ | See [[icecondor: | ||
== terms == | == terms == | ||
Line 54: | Line 62: | ||
== possible directions == | == possible directions == | ||
- | Distributed. Each IceCondor installation (node) uses a distributed hash table to store location records. Nodes can be added to the network easily and once added, its data is searchable by any other node. Using a DHT for storage would loose the benefits of postGIS for lat/long queries. | + | Distributed. Each IceCondor installation (node) uses a distributed hash table to store location records. Nodes can be added to the network easily and once added, its data is searchable by any other node. Using a DHT for storage would loose the benefits of postGIS for lat/long queries. |
+ | ===== Level 2 Headline ===== | ||
icecondor.txt · Last modified: 2024/01/31 04:08 by 127.0.0.1