Skip to content

Latest commit

 

History

History
18 lines (16 loc) · 2.44 KB

TODO.md

File metadata and controls

18 lines (16 loc) · 2.44 KB

TODO

This is a list of things that are known to be missing, or ideas that could be implemented. Feel free to pick up any of these if you wish to contribute.

  • Flesh out the server and client SDK with tooling for ease if use.
    • Make it even easier to implement custom node managers.
  • Support for StructureWithOptionalFields and Union in the encoding macros.
  • Implement Part 4 7.41.2.3, encrypted secrets. We currently only support legacy secrets. We should also support more encryption algorithms for secrets.
  • Write some form of support for IssuedToken based authentication on the client.
  • Implement a better framework for security checks on the server.
  • Write a sophisticated server example with a persistent store. This would be a great way to verify the flexibility of the server.
  • Write some "bad ideas" servers, it would be nice to showcase how flexible this is.
  • Re-implement XML. The current approach using roxmltree is easy to write, but not actually what we need if we really wanted to implement OPC-UA XML encoding. A stream-based low level XML parser like quick-xml would probably be a better option. An implementation could probably borrow a lot from the JSON implementation.
  • Write a framework for method calls. The foundation for this has been laid with TryFromVariant, if we really wanted to we could use clever trait magic to let users simply define a rust method that takes in values that each implement a trait MethodArg, with a blanket impl for TryFromVariant, and return a tuple of results. Could be really powerful, but methods are a little niche.
  • Implement Query. I never got around to this, because the service is just so complex. Currently there is no way to actually implement it, since it won't work unless all node managers implement it, and the core node managers don't.
  • Look into running certain services concurrently. Currently they are sequential because that makes everything much simpler, but the services that don't have any cross node-manager interaction could run on all node managers concurrently.
  • Use NodeSet2 file for types code gen instead of the .bsd file. There is some info here (like data types being abstract), that you can't get from anywhere else.
    • In general, the codegen could use some more work. The current approach isn't really ideal. We should probably unify all the different code gen targets, since they generally depend on a lot of the same data and we risk reading the same data multiple times.