Structural or Behaviour commonalities - Object

Responding to Danths...

> Hello: This is what Iam trying to do
> * smart client using two different databases on the client and for the
> server(web)
> * building different types of activities e.g. emailActivity,
> PhoneActivity, FaxActivity and so on which all have few similar
> structural attributes
> * used an abstract factory during creation of such objects and run
> operations on them ( no problem )
>
> However the implementation of those operations is pretty different in
> the two domains ( client and the server). Further more there are few
> activities which are slight variations of teh existing activities like
> VoiceMailActivity which has similar characteristics to a PhoneActivity
> but not quite similar. The behavioural characteristics(Load, Save,
> Delete, Process etc.) between the domains are similar but the
> implementations would be completely different.
> So without creating a multitiered object hierarchy are there any ways
> to simplify the object creation process.

It seems like straight forward generalization:

[Activity]
A
|
+----------------+----------------+
| | |
[Email] [Audio] [Fax]
+ Load
+ Save
...
A
|
+----------+----------+
| |
[Phone] [VoiceMail]

Since the client and server are essentially independent applications,
the abstractions will be implemented differently in each application.
Since the abstractions are completely independent between applications
one would expect at least some different properties, if not some
different objects.

IOW, I don't see any need for thinking in terms of tiers and attempting
a one-size-fits-all hierarchy would probably be a mistake. Just let the
applications communicate with simple data transfer messages and let each
application interpret the data in terms of the local abstractions.

The GoF's "Design Patterns" provide a number of construction patterns
that might apply, depending on the construction context.


*************
There is nothing wrong with me that could
not be cured by a capful of Drano.

H. S. Lahman
hsl{}pathfindermda.com
Pathfinder Solutions
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
"Model-Based Translation: The Next Step in Agile Development". Email
info{}pathfindermda.com for your copy.
Pathfinder is hiring:
http://www.pathfindermda.com/about_us/careers_pos3.php.
(888)OOA-PATH