Difference between revisions of "Archiving"
Jump to navigation
Jump to search
m |
|||
| Line 1: | Line 1: | ||
== Allowing objects to be archived == | == Allowing objects to be archived == | ||
| − | To permit an object to be archived (also known as serialisation) its class needs to implement the NSCoding protocol. This protocol exposes two methods: -encoderWithCoder and -initWithCoder:. By implementing these methods, your object can be serialised/deserialised as well as sent over GNUstep's Distributed objects mechanism. | + | To permit an object to be archived (also known as serialisation) its class needs to implement the NSCoding protocol. This protocol exposes two methods: -encoderWithCoder and -initWithCoder:. By implementing these methods, your object can be serialised/deserialised (for [[plist]]s or RPC) as well as sent over GNUstep's Distributed objects mechanism. |
See the reference manual for more details. | See the reference manual for more details. | ||
Latest revision as of 07:41, 21 July 2012
Allowing objects to be archived
To permit an object to be archived (also known as serialisation) its class needs to implement the NSCoding protocol. This protocol exposes two methods: -encoderWithCoder and -initWithCoder:. By implementing these methods, your object can be serialised/deserialised (for plists or RPC) as well as sent over GNUstep's Distributed objects mechanism.
See the reference manual for more details.