mirror of
https://github.com/EiffelSoftware/eiffel-org.git
synced 2025-12-07 15:22:31 +01:00
m Additional info in SED note.
Author:halw Date:2010-11-06T16:31:43.000000Z git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@699 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
@@ -68,7 +68,7 @@ In many cases, what you will want to send and receive is not just simple values
|
||||
The basic mechanism enabling a system to send objects through EiffelNet is also the basic mechanism for storing objects into a file: class <code>STORABLE</code> from EiffelBase.
|
||||
|
||||
|
||||
{{note|Although this discussion uses the class <code>STORABLE</code>, it should be noted that this class will in the future be made obsolete by the classes in the Serialization (SED) subcluster of EiffelBase.}}
|
||||
{{note|Although this discussion uses the class <code>STORABLE</code>, it should be noted that this class will in the future be made obsolete by the classes in the Serialization (SED) subcluster of EiffelBase. You will notice that the EiffelNet examples delivered with EiffelStudio use the classes from the Serialization cluster.}}
|
||||
|
||||
|
||||
As documented in [ [[Bibliography|2]] ], <code>STORABLE</code> provides features to store and retrieve complete object structures. There are three storage procedures, called under the respective forms
|
||||
|
||||
Reference in New Issue
Block a user