If you want the browser to refresh the page automatically, then you
can set a meta-refresh:
response.refresh = ...
If you want to invalidate caches, then you can do this within Apache:
> 2. How to display the map with markers?
map = gis.show_map(...)
> 3. Retrieving and counting data entries, should such task better be
> implemented using controllers?
Yes, I would include the db lookups in the index() controller & pass
back a snippet of HTML to the view...
You may want to consider setting up multiple servers.
Multiple webservers for load-balancing is easy, but can also keep one
just for core team.
Whilst the writable database can only be on one server, it is a good
idea to replicate this to a backup server anyway.
If the normal public don't write, their views can be generated from
this backup copy.
With a little work, the odd writable forms they have to submit
requests could be sent to the main DB.
db = (slave db for reads)
db2 = (master db for writes) <- then amend the odd writable forms to
use this db2 instead of db.
The server used by internal staff could simple have db2 = db
> 2. The update frequency for twitter should be higher than map. How is
> this for now?
// Default time in milliseconds for the feed to be reloaded.
GFdynamicFeedControl.DEFAULT_FEED_CYCLE_TIME = 1800000;
=> every 30 minutes
I pushed this down to 5 minutes in Trunk I think & this also exposes
the setting to Sahana:
Note that this is all done within the clients, so doesn't add any
extra load to the main server :)
> 3. Not all layer of map will be displayed on HP, 2 would be maximan.
The Map API is fully-configurable :)