Re: History on WO query: Is there a special name for the design pattern describes EO itself?
Re: History on WO query: Is there a special name for the design pattern describes EO itself?
- Subject: Re: History on WO query: Is there a special name for the design pattern describes EO itself?
- From: Daniel Beatty <email@hidden>
- Date: Mon, 04 Aug 2008 20:42:07 -0500
Greetings Chuck,
LOL. I happen to have a copy of that issue of Queue (aka the last
issue of Queue in paper print). I tend to agree with you, and of
course I was reading it to glean a reference that would further
contribute to my papers that I am writing. Naturally, it would seem
fascinating to have published my article in that issue of Queue as it
would been a simple example of these design patterns. Of course,
it seems I have been challenged by my own fascinations.
Georg recalled and told me a story about the Gamma et all book on
Design Patterns. He said that it was influenced by the work at NeXT
and the patterns that remained undocumented outside of NeXT up until
that point. What strikes me as odd today is how slowly the point and
foundation of that concept has permeated academia.
That being said, Chuck would you and the others in the WO community
like to make review of the most recent revisions to my first two
papers. There is one composite pattern that i am naming the model-
entity-attribute-relationship pattern for lack of a previous and
general name for it (covering the EO framework). While EO is a
ORM, it is unique in its separations. Not only does EO generate code
(html, java, sql, JSON, etc), but it combines the separation in the
model self along with the MVC pattern implemented in WO that is
difficult categorize much less summarize. Hopefully, these two papers
can start to change that.
The Sky Raider project (http://venus.cs.ttu.edu/groups/skyraider)
hopefully illustrates and capitalizes on WO+EO's innovative features
with ideas of my own. The two papers are located at:
https://venus.cs.ttu.edu/svn/IQSCMS/CMSTechniques/CMSTechniques.pdf
https://venus.cs.ttu.edu/svn/iFITSDocuments/FIREWGBridging/bridging.pdf
Thank you,
Dan
On Aug 4, 2008, at 2:18 PM, Chuck Hill wrote:
is an implementation of a larger architecture called Object -
Relational Mapping (ORM). The latest addition of ACM's Queue
magazine was dedicated to ORM. There are a number of interesting
articles and they will probably also point you to other references
on the topic. Reading the issue made me realize how many things EOF
got right (EOF is never mentioned). It reinforced my decision to
stay with EOF. :-)
Dan Beatty, M.S. CS (B.S. EECS)
Ph.D. Student
Texas Tech University
email@hidden
http://venus.cs.ttu.edu/~dabeatty
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden