Re: Designing issue
- From: "mojtaba_danai@xxxxxxxxx" <mojtaba_danai@xxxxxxxxx>
- Date: 29 Jun 2006 21:48:28 -0700
Hi
The original message was this:
I am trying to make a adapter program.
-There can be different kind of adapters, which each can take data from
one source.
-It should be possible to plugin the new adapter for a new source of
data.
-The adapters all make a common structure to give it to the connected
clients. (I have implemented this part).
-Each adapter uses a specific API to collect data from data source.
How the design of the adapter class should look like? Which design
pattern?
There should probably be a superclass for all adapters, right? But they
use different APIs, as I said before, and one of the adapters inherits
already from couple of data source API classes.
Thanks.
Regards
mojtaba
mojtaba_danai@xxxxxxxxx wrote:
Hi
Thanks for the answer. Then, what is the good approach to this problem?
Making plugable adapters?
Regards
mojtaba
Phlip wrote:
mojtaba_danai wrote:
There should probably be a superclass for all adapters, right?
Why? Will anything ever use a reference to this superclass, not knowing
which derived type it wields?
Design is not about abstracting everything, it's about defining minimal and
useful interfaces.
--
Phlip
http://c2.com/cgi/wiki?ZeekLand <-- NOT a blog!!!
.
- Prev by Date: Design
- Next by Date: Re: Object identity
- Previous by thread: Design
- Next by thread: Re: Bob's 'Self-aggrandizing ignorant' Count: Was: What databases have taught me
- Index(es):
Relevant Pages
|