This project has moved. For the latest updates, please go here.

Dynamically creating Input Adapters... Possible?

Apr 26, 2011 at 1:57 PM
Edited Apr 27, 2011 at 1:11 PM

Does the openPDC framework allow input adapter instances to be created "on-the-fly" to deal with different sources of data?

We have a scenario where a number of legacy "historian-like" databases exist and information from these databases needs to be brought into openPDC to complete certain calculations.

As requests for these calculated data streams come in, we would like to create connections to the various services using input adapters, and then remove them once the requests are terminated.

Is this the correct approach for the openPDC architecture, or is there a better way?


Apr 29, 2011 at 7:19 PM

Yes, if you manage them yourself internally - an example of this is the DataPublisher adapter within the TFS transport namespace.

Since collections of adapters also implement IAdapter, they in turn can be a loaded adapter.

The collection can then manage its own dynamic collection of adapters - adding and removing them dynamically.


May 2, 2011 at 2:17 PM
Edited May 2, 2011 at 2:17 PM

Thanks - that makes sense.

Is there any reason why the adapters I want to create could not be action adapters?

Then I could just use the existing collection inside the publisher.


May 2, 2011 at 5:17 PM

No issues with an action adapter, see the intended notions for adapters below.

Depending on what are trying accomplish and/or how you are intending on using the items it might be possible to add items to existing collection - but it may be easier to create your own modeled after the existing code.