http:^^www.cs.wisc.edu^shore^

来自「This data set contains WWW-pages collect」· EDU^SHORE^ 代码 · 共 367 行 · 第 1/2 页

<H3>Support for Existing, File-based Applications</H3>

A major goal of SHORE is to enable applications that currently
use untyped, byte-oriented files for their persistent data,
flattening and un-flattening their data each time it is accessed,
to stop doing so.
Such applications should be able to store their data as typed, structured
objects for more convenient, type-safe, intra- and inter-program data sharing.
Our ultimate hope is that SHORE will displace byte-oriented
file systems such as the Unix file system.
<P>
SHORE provides two major services from a file system standpoint.  First,
to support object naming and space management in a world with many
persistent objects, SHORE provides a flexible, tree-structured,
Unix-like name-space in which all persistent objects are reachable,
either directly or indirectly.  Doing so gives SHORE users
a familiar framework in which to register individual
persistent objects (termed "registered" objects), the roots of
large persistent data structures, or bulk sets of unnamed objects (termed
"anonymous" objects).  The realization of this framework involves
several different kinds of SHORE file system objects, including
directories, pools (which are files containing anonymous objects),
symbolic links, and cross references.
<P>
SHORE provides two mechanisms to ease the transition of legacy Unix
applications such as compilers, editors, and CAD systems from
traditional byte-stream files to SHORE.
First, for applications that can be re-linked, SHORE provides a standard
Unix-compatible file system interface  (e.g. open, close, read,
write, mkdir, chdir,.).
In order to make access to SHORE objects via Unix file system calls
possible, the definer of a SHORE object type can optionally designate one
variable-length byte string or character string attribute of the object as
being the object's "Unix data".  Programs that attempt to read an object
through SHORE counterparts of the Unix file system calls
will only see this portion of the object. For legacy programs that
wish to do so without being re-linked, it is possible to NFS-mount a
SHORE file system and access the Unix data
contained in its objects directly.  This makes it feasible for both
new and old applications to access the same set of objects.
While old applications can only access the "Unix data" component
of the object, new applications can define and access other, more
structured, attributes of the object.

<HR>

<H2>
<A NAME="Release">Release Information:</A>
</H2>
Below is the latest time table for the release of SHORE. 
These dates are approximate and subject to change.
If you have any questions, contact 
<ADDRESS>
[e-mail].
</ADDRESS>

<H3> Beta Release (0.9)</H3>
On May 3, 1995 we had our first beta release.

<H3> Beta Release (0.9.3)</H3>
<!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><!WA23><A HREF="http://www.cs.wisc.edu/shore/beta.html">
The second Beta-rlease of Shore (version 0.9.3)
</A> is now available (Sept 18, 1995).
It includes improved documentation, more complete
implementations of many SDL features, many bug fixes, and ports to
Solaris, HP-UX, Linux.

<H3> Version 1.0 </H3>
On August 6, 1995 we released <!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><!WA24><A HREF="http://www.cs.wisc.edu/shore/1.0/shore.html">Shore, version 1.0.</A>
Gzip'd tar files of the source, documentation and a binary release (sparc and
pentium solaris 2.5), can be found at
<!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><!WA25><A HREF="ftp://ftp.cs.wisc.edu/shore/1.0/">
&lt;ftp://ftp.cs.wisc.edu/shore/1.0/&gt;
</A>.

<HR>

<H2>
<A NAME="mail">Mailing Lists</A>
</H2>
There are two Shore-related mailing lists: 
<em>
[e-mail]
</em>
and 
<em>
[e-mail]
</em>.
<P>

<H3>[e-mail]</H3>
This mailing list reaches the Shore development team.  
It is for use
by Shore users to submit questions, comments, and bug reports to us.
You cannot subscribe to this mailing list.
<HR>

<H3> [e-mail] </H3>
This is a mailing list for users of (and those interested in) SHORE.
This list is managed by the listproc software at the UW-Madison
CS department.  It is currently unmoderated, but in the unlikely
event that it gets cluttered with junk mail we will moderate it.
mail messages.  If you are interested in the list, but your mailbox is
already too cluttered, you can sign up for weekly digests.  See below
for more information.  More information about the list will be sent
when you subscribe.  <P>

<H4> Purpose of shore_all </H4>
<UL>
<LI> Notifying interested parties of new releases and other changes in the Shore ftp archive
<LI> Requests for help from other users 
</UL>

By default, replies will be sent only to the sender, rather than being
posted to the entire list.  If you want the entire list to see your
reply, just copy the reply to shore_all.
<P>

This list is an <em>public</em> mailing list.  Thus, anyone may
subscribe to it.  Only subscribers may post to the list.  The existence
of this list is shown in the listing returned by listproc when
it processes a <tt>LISTS</tt> request.  When you subscribe, your
subscription is "concealed" by default.  That is, other subscribers
cannot obtain the membership list from the listproc system.  <P>

<H4> Subscribing to shore_all </H4>
<P>
To subscribe or to change your subscription, you must mail a special
message to: <tt>[e-mail]</tt>.
<UL>
<LI> To subscribe, the content of the message should look like this:<BR>
    <tt>subscribe shore_all <Your Full Name></tt>
<LI> To receive weekly digests (rather than individual messages), send
this along with your subscription (or send it in a separate
 message):<BR>
    <tt>set shore_all mail digest</tt>
<LI> To un-subscribe, the content of the message should be:<BR>
    <tt>unsubscribe shore_all</tt>
<LI> To get help on the list processor, the content of the message
should be: <BR>
    <tt>help</tt>
</UL>

<H2>Last Modified:</H2>
Mon Mar 18 10:41:39 CST 1996
<P>

<ADDRESS>
Nancy Hall
/ [e-mail].
</ADDRESS>

<HR>

<H2>Footnotes: </H2>
<DL><A NAME=foot1><DT>... compatibility with ODL<DD>
SHORE and ODMG concurrently decided to use the OMG data model
IDL as the starting point for their data models.  Hence SDL and ODL
are very similar to one another.  Once ODL stabilizes
we can convert SDL to be 100% compatible with ODL.

<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
<BR>

</BODY>
</HTML>