| … | … | @@ -19,10 +19,19 @@ An assortment of other interesting odds and ends can be found here. |
| 19 | 19 | This is ***version 4.3.0***. Multiple projects depend on this; |
| 20 | 20 | everything works; all unit tests pass. There is a very long and boring |
| 21 | 21 | list of changes since January 2025; all of these are bug fixes or |
| 22 | | patches forced by updates to the core AtomSpace. Perhaps the most |
| 23 | | important change is that `cog-delete` only deletes Atoms in the remote |
| 24 | | AtomSpace. Deleting in the local AtomSpace must now be performed as a |
| 25 | | distinct step. |
| 22 | patches forced by updates to the core AtomSpace. |
| 23 | |
| 24 | The most notable changes are: |
| 25 | * The `*-delete-*` message only deletes Atoms from the remote AtomSpace. |
| 26 | Deleting from the local (in-RAM) AtomSpace must now be performed as |
| 27 | a distinct step. |
| 28 | * The base `StorageNode` now uses a message-passing system to perform |
| 29 | all actions. Typical messages include `*-open-*`, `*-close-*`, |
| 30 | `*-load-atom-*`, `*-store-atom-*` and so on. See the wiki page |
| 31 | for [StorageNode](https://wiki.opencog.org/w/StorageNode) to get |
| 32 | a general description, and |
| 33 | [ObjectNode](https://wiki.opencog.org/w/ObjectNode) for message |
| 34 | specifics. |
| 26 | 35 | |
| 27 | 36 | ### Alternatives |
| 28 | 37 | The `StorageNode` API is the original, primary API for moving Atoms |