Archiving
From GNUstepWiki
(Difference between revisions)
| Revision as of 06:40, 22 November 2005 Quineska (Talk | contribs) Added page with NSCoding details ← Previous diff |
Current revision Awiebe (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| == Allowing objects to be archived == | == Allowing objects to be archived == | ||
| - | To permit an object be archived (also known as serialised) it's 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. | ||
Current revision
[edit]
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.
