BrowsingContext allows for the user to declare a single, or multiple, type(s) of services they are interested in and poll the instance to get discovered Services.

Usage of this might look something like:

let ctx: BrowsingContext = BrowsingContext::new().query("_http._tcp.local").query("_http-alt._tcp.local").search();
let mut services = vec![];

loop {
    if let Some(service) = ctx.poll() {
        services.push(service);
    }

    // ...
}

I take inspiration to other APIs that do similar things, such as sockets, IO, etc., and have a sort of queue-based polling system which I think works well for now. If not, I can change it at a later date, but it will suffice for an initial implementation.

Although it was interesting to experiment with BitVecs, I realize that I don't use their functionality much and they've become unnecessary.

Revert to using Vec<u8> with more bitwise operations to extract values.

Tasks:

• Revert to Vec
• Private all fields on structs and add getters and builder-setters instead.

The project is at a state wherein pretty much all of the lower-level functionality, parsing and packing of DNS Packets, is implemented in a functional way. Because of this, we can now write browsing functionality so users of the library don't need to manually compose and send the packets.

This is more of a meta-issue or an initializer for the initial fleshing out of this functionality. It's fairly simple to implement but I want multithreading support which I need to look into more.

Tasks:

• Tighten packet-related visibility so that it is not user facing anymore.
• Write an BrowsingContext struct that asynchronously browses for services that the user can consume.
• Parse TXT and SRV records into Service structs.

There is a ton of repeated code then can be easily abstracted away with a proc_macro_derive.

Convert the current binary crate into a library and re-implement the user-facing functionality into an example.