F
farseer
i'm looking for the right solution to my problem.
i have an app that uses certain core set of data object that it knows
about and operates on. The source of the actually data however may
come from various sources, including webservices, that return that data
in their own objects. So to keep my application operating on the
objects it only knows, i need to transform the incoming data objects
into my app's data objects. important: The incoming data objects do
not support a common interface.
I thought an Adapter or Bridge pattern would be ideal here, but i
realize that for ever new datasource, i may have to add more and more
adapters..is that good design? are there better alternatives?
i have an app that uses certain core set of data object that it knows
about and operates on. The source of the actually data however may
come from various sources, including webservices, that return that data
in their own objects. So to keep my application operating on the
objects it only knows, i need to transform the incoming data objects
into my app's data objects. important: The incoming data objects do
not support a common interface.
I thought an Adapter or Bridge pattern would be ideal here, but i
realize that for ever new datasource, i may have to add more and more
adapters..is that good design? are there better alternatives?