================================================================
(C-lib  tine32.dll, etc. : SVN 2865)  Release 4.3.4

- Overall attention level GREEN 

- NOTE: No 'major' header changes

- Bug Fix (Local Histories): Fixed a problem retrieving history data with 
  explicit raster sample = 1 (the fill and repeat strategy).

  Affects:		local history subystem

  Possible side effects: None expected.

  Attention level:       GREEN

- Feature Fix: An attempt to write a globals keyword variable is now
  trapped at the client and returns 'illegal_read_write'.

  Affects:		Globals calls.

  Possible side effects: None expected.

  Attention level:       GREEN

- Bug Fix: The call GetPortOffset() now returns '1' if no fec manifest is found.
  The fec manifest is then created when the server finishes initializing.
  Previously when no manifest existed, a 'no_such_file' error message prevented 
  the call from working.
  
  Affects:		calls to GetPortOffset()

  Possible side effects: None expected.

  Attention level:       GREEN

- Bug Fix: The new API call 'GetValidDeviceNumber()' is now used internally
  to obtain a device number from a device string. When this call is used,
  strings such as "#67" will only return the parsed number '67' IF
  there are at least this many devices registered.  Otherwise it returns an
  error (-illegal_device)

  This was a potential problem in queries to get the property information.

  Affects:		Queries to property information (stock property PROPERTIES).

  Possible side effects: None expected.

  Attention level:       GREEN

- New Feature: Additional data types CF_DBLTIME and CF_NAME64TIME are available
  as strong type alternatives to CF_DBLDBL and CF_NAME64DBL where local history
  calls are concerned (not yet available in the central archiver).

  Client-Side: The 'toString()' operation will display the second double value
  as a time stamp if for example the data type CF_DBLTIME is used instead of CF_DBLDBL.

  Server-side: If local history properties are obtained and stored as CF_DBLTIME 
  or CF_NAME64TIME, then the second stored double value is used as the returned
  timestamp in local history calls.

  Affects:		Local history information

  Possible side effects: None expected.

  Attention level:       GREEN

- New Feature: The current version is now 4.3.4

  Affects:		Current Library Version

  Possible side effects: None expected.

  Attention level:       GREEN

================================================================
(java-lib  tine.jar : SVN 52725)  Release 4.3.4

- New Feature: The method appendHistoryData() (introduced in last release)
  is now used to fill the short-term storage with data from the central 
  archive IF a local history parameter has no long term storage but maintains
  a short term storage of more than 4 hours.

  Affects:		local history subystem

  Possible side effects: None expected.

  Attention level:       GREEN

- Bug Fix (Local Histories): Fixed a problem retrieving history data with 
  explicit raster sample = 1 (fill and repeat strategy).

  Affects:		local history subystem

  Possible side effects: None expected.

  Attention level:       GREEN

- Bug Fix (Local Histories): Scheduling local history data
  now works properly

  Affects:		local history subystem

  Possible side effects: None expected.

  Attention level:       GREEN

- Feature Fix: An attempt to write a globals keyword variable is now
  trapped at the client and returns 'illegal_read_write'.

  Affects:		Globals calls.

  Possible side effects: None expected.

  Attention level:       GREEN

- New Feature: Additional data types CF_DBLTIME and CF_NAME64TIME are available
  as strong type alternatives to CF_DBLDBL and CF_NAME64DBL where local history
  calls are concerned (not yet available in the central archiver).

  Client-Side: The 'toString()' operation will display the second double value
  as a time stamp if for example the data type CF_DBLTIME is used instead of CF_DBLDBL.

  Server-side: If local history properties are obtained and stored as CF_DBLTIME 
  or CF_NAME64TIME, then the second stored double value is used as the returned
  timestamp in local history calls.

  Affects:		Local history information

  Possible side effects: None expected.

  Attention level:       GREEN

- New Feature: The current version is now 4.3.4

  Affects:		Current Library Version

  Possible side effects: None expected.

  Attention level:       GREEN