1. distributed business objects and granularity design
We recently purchased an application server (java ejb based), and as
part of the product they sent us a prototype - example application.
Part of the application was a domain partitioning framework that I
find both interesting and perplexing at the same time. I'd like to
hear what you guys think about their approach, and my thoughts on
They essentially build their domain objects with the following concer
DomainObject DomainIdentity DomainState
The identity is just the displayable name of the object (for filling
in select lists, et), the state is the bare bones of the object (used
for distribution), and the object is a completely reified domain
object. The domain object and state keep a pointer to the identity,
and the object keeps a pointer to the state.
Asci art sucks in a relative font so I bear with me
DomainObject ----> DomainState ------> DomainIdentity
Hopefully that somewhat conveys the picture.
Here's my take on it. While a very useful seperation, it isn't OO.
A DomainObject ISA DomainState which ISA DomainIdentity. In c++ you
could use MI and still get nice clean seperation, and good inheritance
based abstraction. In java you're screwed. And should do this
Which means that each cannot have its own base class for shared
functionality -- which is pretty lame. But at least you do get
functional polymorphism. Its an interesting quandary -- at least to
me. Has anyone come up with other neat ways to seperate object
"reified -ness" (a new word?) for distribution overhead reduction.
If this has already been beaten to death on this forum, I apologize, I
don't read (or post) much anymore.
2. USR winmodem 56K PCI
3. Object - Oriented Design and Performance in Business Cases
4. VLIW (TI c6x) vs. CISC vs. RISC
5. Business Object Design for Telecoms domain
6. Public test phase of F-PROT Professional for Windows NT, 95 and OS/2
7. Designing Business Objects
8. OOPSLA'95 Workshop on Business Object Design and Implementation
9. Abstract design of Report Accounts [RA] in Business Object Notation [BON]
10. OOPSLA Workshop on Business Object Design and Implementation
11. OOPSLA Workshop: Business Object Design and Implementation
12. OOPSLA Workshop 26: Business Object Design and Implementation