Changes between Version 15 and Version 16 of proposals/readonly

Timestamp:

Mar 20, 2013, 7:41:32 AM (11 years ago)

Author:

heikki

Comment:

--

proposals/readonly

@@ -3 +3 @@
 || '''Date''' || 2013-01-22 ||
 || '''Contact(s)''' || Heikki Doeleman ||
-|| '''Status''' || Implemented and tested ||
+|| '''Status''' || Done ||
 || '''Assigned to release''' || 2.9.x ||
 || '''Resources''' || Available (funding EEA) ||
@@ -44 +44 @@
 === determining read-only status ===
 
-The read-only status of GeoNetwork is determined by a periodic 'DB heartbeat' that attempts to write (and delete) a value in the database. If the situation changes (i.e. GN is not read-only but fails to write, or GN is read-only but succeeds writing) the read-only status of GN is dynamically adapted. The heartbeat's initial and fixed delay in seconds can be set in config.xml and have default values 5 and 60.
+The read-only status of GeoNetwork is determined by a periodic 'DB heartbeat' that attempts to write (and delete) a value in the database. If the situation changes (i.e. GN is not read-only but fails to write, or GN is read-only but succeeds writing) the read-only status of GN is dynamically adapted. The heartbeat's initial and fixed delay in seconds can be set in config.xml and have default values 5 and 60. The heartbeat is disabled by default and can be enabled in config.xml by setting parameter DBHeartBeatEnabled to true.
 
 === other changes ===
 
 There are cases where the DB-writing part of a service is that small that it is better to restrict these writes at a level below the service, to still allow the service to run also in read-only mode. An example is metadata view: this service write to the DB updating the metadata's popularity. Even so it is not made a !NotInReadOnlyModeService, so also in read-only mode you can still use this service; instead the db-writing part is made conditional on readonly state at a level below the service. (of course this may be seen as a design flaw in the service behaviour and you could argue that there should exist a separate service to update the popularity -- but refactoring is outside the scope of this proposal). 
+
+=== Capabilities ===
+
+When GeoNetwork is in read-only mode, the CSW Publication operations (Transaction and Harvest) are not returned in response to a CSW !GetCapabilities request.
 
 === GUI ===