User Tools

Site Tools


icecondor

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
icecondor [2008/11/29 20:48]
97.115.94.205
icecondor [2008/12/28 12:39]
71.237.252.103
Line 7: Line 7:
 See [[icecondor:androidclient]] \\ See [[icecondor:androidclient]] \\
 See [[icecondor:news]] \\ See [[icecondor:news]] \\
-See [[icecondor:benchmark]]+See server [[icecondor:benchmarks]] \\ 
 +See [[icecondor:battery]] usage \\ 
 +See [[icecondor:URLs]] \\ 
 +See [[icecondor:pigeon]] \\ 
 +See [[icecondor:graphics]] \\ 
 +See [[icecondor:roadmap]] 
  
 == terms == == terms ==
Line 44: 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 ==
Line 59: Line 67:
 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 ===== 
  
icecondor.txt · Last modified: 2016/06/25 11:25 (external edit)