IAddon boundary for hive-fressian (library-kind addon: contributes a serialization capability, no tools). Hosts discover the registry/codec through the capability; consumers call the namespaces directly.
IAddon boundary for hive-fressian (library-kind addon: contributes a serialization capability, no tools). Hosts discover the registry/codec through the capability; consumers call the namespaces directly.
Envelope codec: one durable Fressian file = header map + item stream.
Layout (in stream order): header, item-count, items. Handlers resolve through hive-fressian.registry at call time, so any domain registered before the call serializes transparently.
Envelope codec: one durable Fressian file = header map + item stream. Layout (in stream order): header, item-count, items. Handlers resolve through hive-fressian.registry at call time, so any domain registered before the call serializes transparently.
Handler-domain registry — the OCP swap point of hive-fressian.
A DOMAIN is a named bundle of Fressian handlers for one family of types: {:write-handlers {Class {"tag" org.fressian.handlers.WriteHandler}} :read-handlers {"tag" org.fressian.handlers.ReadHandler}}
Consumers register their domain once (register!); every codec built afterwards sees the merged handler maps. New type family = new domain, zero change to the codec.
Handler-domain registry — the OCP swap point of hive-fressian.
A DOMAIN is a named bundle of Fressian handlers for one family of types:
{:write-handlers {Class {"tag" org.fressian.handlers.WriteHandler}}
:read-handlers {"tag" org.fressian.handlers.ReadHandler}}
Consumers register their domain once (register!); every codec built
afterwards sees the merged handler maps. New type family = new domain,
zero change to the codec.cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |