One of the groups in CS 141 this term is working on a project
to provide transparent access to remote objects, implemented
in Java over RMI. As part of the background research, I'd like
them to investigate the facet of NeXT's PDO that provides that
functionality.
A web search yielded me the following nuggets...
http://www.next.com/NeXTanswers/HTMLFiles/1928.htmld/1928.html
presents a pretty good overview of the NEXTSTEP/OpenStep
object model from a high level viewpoint. Then,
http://www.next.com/NeXTanswers/HTMLFiles/1592.htmld/1592.html
gives me a decent overview of PDO, but isn't really anecdotal.
So we look to
http://www.next.com/NeXTanswers/HTMLFiles/1992.htmld/1992.html
and
http://www.next.com/OpenStep/Products/PDO/drdobbs.8.95.html
which are good, ancedotal presentations of designing apps
using NeXT's distributed object techonologies. (Historical
note: The Dr Dobbs article is written by FoRK's very own Ernie
Prabhakar, who mentions Mecca as a starting point for competition
"against Taligent and Cairo in 1996 or 1997"... :)
My question to FoRK is this: do you know any other good references
that describe PDO (low level or high level, I'll take either), so
I can pass them along to the group? Thanks in advance!
Adam
----
adam@cs.caltech.edu
I want *actual* OOFSes: *not* files with new stat() bits, *but* real,
named, filterable, convertible objects... And: everything is an object;
every object has a declarative UI; every object is secure, authenticated,
virtualizable, sharable, archivable, and alive! I want Objects in the
rearview mirror to be SMARTER than they appear!! And I want this NOW!!!
-- Rohit Khare