This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
icecondor [2008/12/28 12:27] 71.237.252.103 |
icecondor [2011/01/27 13:29] donpdonp |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== IceCondor: | + | ===== IceCondor: |
See http:// | See http:// | ||
Line 49: | Line 49: | ||
* erlang | * erlang | ||
* ruby | * ruby | ||
+ | * java | ||
database: | database: | ||
* postgresql + postGIS extension | * postgresql + postGIS extension | ||
+ | * couchdb | ||
access protocols: | access protocols: | ||
* HTML | * HTML | ||
* XMPP | * XMPP | ||
+ | * OAUTH / OpenID | ||
== URLs == | == URLs == | ||
object being tracked: / | object being tracked: / | ||
- | track point: /trackpoint/< | + | one object at one location: /location/< |
== 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. Hadoop? | 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. Hadoop? | ||
- | ===== Level 2 Headline ===== | ||