Skip to content

Conversation

@ross-spencer
Copy link
Collaborator

@ross-spencer ross-spencer commented Sep 21, 2025

Following on from the roy optimization last week, I have created a wasm implementation of roy. This PR might be a useful jumping off point for a conversation with most of the work done in pronom_byte_array_helpers.go. In the WASM file we're now able to create a signature file at runtime using embedded defaults. These can also be updated more easily in the future.

I looked at removing the static package and see it's used by github.com/richardlehane/siegfried/pkg/lib but maybe there's another way of improving that API with updated roy work?

Let me know what might need changing, e.g. maybe some of the light duplication in pronom_byte_array_helpers.go can better be done in the existing pronom.go functions?

No rush on my end, I have to move focus onto the workshop this proof of concept is for but will try following up on anything asap.

TODO

  • Ensure container signatures work.
  • Ensure that if we fork between using a iostream or file that the remainder of the signature loading process does not repeat itself creating redundancy.
  • Make sure the new mechanism is compatible with Siegfreid's existing interfaces/API.

@ross-spencer ross-spencer changed the title WASM Roy WIP: WASM Roy Nov 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant