Before I asked the
question, I thought of the object domain much as Casey has said:
"I think of an object domain as just the set of objects which implements a feature or solves a problem."
Thanks to Chris, David and Casey for adding more detail and different viewpoints. It all helps to improve my understanding.
Send Beginners mailing list submissions to
[hidden email]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.squeakfoundation.org/mailman/listinfo/beginners
or, via email, send a message with subject or body 'help' to
[hidden email]
You can reach the person managing the list at
[hidden email]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Beginners digest..."
Today's Topics:
1. Re: Object Domain (Casey Ransberger)
----------------------------------------------------------------------
Message: 1
Date: Sat, 7 Jul 2012 10:17:51 -0700
From: Casey Ransberger [hidden email]
Subject: Re: [Newbies] Object Domain
To: [hidden email] [hidden email], "A friendly
place to get answers to eventhe most basic questions about Squeak."
[hidden email]
Message-ID: [hidden email]
Content-Type: text/plain; charset=us-ascii
I agree with David's statement below, generally. It's worth noting that in Smalltalk, our object memory + virtual machine together serve as a kind of non-relational database which preserves both state and behavior, but one doesn't generally have to think about it and that's beautiful:)
Even in SQL one has triggers and stored procedures, so perhaps the distinction is pervasively arbitrary. Someday we may have fast non-volatile RAM and no separate long term storage, at which point databases and persistence as we popularly think about them may even disappear entirely.
One of Smalltalk's offspring, the Self language, uses message sends (as far as the programmer is concerned) to access state, and thus does away with assignment in the usual/low-level sense. This is fun to think about (for me anyway!)
Someone please correct me if I'm wrong here, but I think of "object domain" and "object model" (where the word model is distinct from and more general than the Model in MVC) as being interchangeable.
I think of an object domain as just the set of objects which implements a feature or solves a problem. I suppose I may have my terminology mixed up though, so sound off if I'm wrong here folks:)
--Casey Ransberger
On Jul 6, 2012, at 2:42 PM, David Mitchell [hidden email] wrote:
I think a lot of people think of the domain as the database, but I've always thought of the database as how you store your domain model, not the domain model itself.
------------------------------
_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
End of Beginners Digest, Vol 75, Issue 4
****************************************
_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners
Locked
