dealing with information. They've mostly augmented those ways and made them more powerful.
In fact, I think many people were using objects before they became popular and supported
by languages. Objects actually have helped make things more connected with real physical
systems. So when the "Next Cool Thing" comes along, I think it will augment objects not replace them.
Remember the importance of objects is the concept, not the code.
I don't see the connection with separating or not domain and persistence layers. If they are separate
they can always be combined. Once they are combined, they are difficult to separate. This is
an entropy problem.
Remember that software ages and needs to be changed over a period of time, so it is the concepts and algorithms that are important.
We have gone through about 5 generations of our software over a period of 8 years. Different languages, platforms,
persistent store, transport, etc., but the underlying concepts have been more constant although improved
over time.
At 05:43 PM 5/18/2001 +0200, [EMAIL PROTECTED] wrote:
> OODBMS are even implemented within the domain layer. They just store
> the objects used by the domain layer as they are - as objects.
I should like to point out that when the Next Cool Thing(tm) comes
along objects just might stop being the most hyped things for
implementing business logic. From which it follows that maybe
it isn't such a good idea after all to not separate domain and
persistence layers even with objects+OODBMS.
regards,
Karsten
--
GPG key ID E4071346 @ certserver.pgp.org
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
Computer and Computational Sciences
Los Alamos National Laboratory
505-665-1907
