Unclear on benefits of code pattern used in toplevel Dirigible module.

[z5h]

In the Dirigible module we see this code:

def self.api(options = {})
  Dirigible::API.new(options)
end

Every time api is referenced, as it is for all Dirigible calls via method_missing, a new API will be instantiated.

Why is this done? Why is there an options hash that (seemingly) can't be modified during these calls?

[anthonator]

The idea is to have the ability to instantiate multiple Dirigible clients. This is useful if you need to interact with multiple UA accounts. For convenience sake you can use Dirigible from a "global" config so you don't have to instantiate and configure a Dirigible client every time you want to make a call. Granted it's an unrealized dream at the moment so it needs some work. I'd also be interested in hearing a better way to accomplish this if you have any thoughts.

[z5h]

Thanks. So the fact that the following calls Dirigible::API.initialize twice is not so much a bug as a not-yet-complete feature?

Dirigible::DeviceRegistration.register_apid(apid1)
Dirigible::DeviceRegistration.register_apid(apid2)

I just wasn't sure if I was missing something. It's not a huge concern for me right now. Just trying to understand a few things.