Skip to content

Requesting resolvers

Benjamin Kappel edited this page Nov 19, 2020 · 2 revisions

Requesting a new Resolvers

One of the benefits of DaAPI is that resolvers are vital yet easy to develop and integrate. Resolvers can be released regardless of the current feature track and find their way into the product within days.

This section helps you to give us the right information to build your resovlers into DaAPI.

Create an issue

The start is to create an issue. The other section is a template to write a good issue.

Providing examples and use cases

Context is essential to validate if our solution is a solution to your problem. Start with what you want to achieve from a resolver.

I need a resolver that is valid for every packet sent by a device from specific manufacture. In most cases, it is only one vendor, but there should be the possibility to resolve to valid if a range of manufacturer sends a packet.

Providing packets that match and don't match the provider

It would be a huge relief to have tcpdump or wireshark trace of packets in both flavors: packets that should pass and those that shouldn't.

Be an early adopter

Resolvers are not complicated to develop and can quickly be tested. Nevertheless, the resolver is our suggestion. We would like to get your feedback if our development solved your problem. If we did it, we would integrate it into the main branch. Otherwise, we go back to the design phase and try a different approach.