By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,852 Members | 2,219 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,852 IT Pros & Developers. It's quick & easy.

Designing issue

P: n/a
Hi

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?

Thanks.

Regards
mojtaba

Jun 30 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Hi again
Just wanted to add:

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

Hi

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?

Thanks.

Regards
mojtaba


Jun 30 '06 #2

P: n/a
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!!!
Jun 30 '06 #3

P: n/a
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!!!


Jun 30 '06 #4

P: n/a
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

mo***********@yahoo.com 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!!!


Jun 30 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.