diff -r 51a74ef9ed63 -r ae94777fff8f Symbian3/SDK/Source/GUID-18D92465-3F62-55CF-8229-EE811FD5F568.dita --- a/Symbian3/SDK/Source/GUID-18D92465-3F62-55CF-8229-EE811FD5F568.dita Wed Mar 31 11:11:55 2010 +0100 +++ b/Symbian3/SDK/Source/GUID-18D92465-3F62-55CF-8229-EE811FD5F568.dita Fri Jun 11 12:39:03 2010 +0100 @@ -1,12 +1,12 @@ - - - - - -Stream networks

When a store stream is created, a stream ID is generated. This ID can be used to open the stream later. Stream IDs can be externalised into another stream, and this allows streams in a store to be built into a network.

An object that is saved to a store may use a network of streams, typically starting with a single head stream.

An object stores itself using a function of the form:

streamId=object.StoreL(store);

Given the correct stream ID, the object may be restored using a function of the form:

object.RestoreL(store,streamId)

where store is a reference or pointer to a store.

The function names StoreL() and RestoreL() are conventional for this purpose.

The following diagram shows the idea of stream networks:

 \ No newline at end of file + + + + + +Stream networks

When a store stream is created, a stream ID is generated. This ID can be used to open the stream later. Stream IDs can be externalised into another stream, and this allows streams in a store to be built into a network.

An object that is saved to a store may use a network of streams, typically starting with a single head stream.

An object stores itself using a function of the form:

streamId=object.StoreL(store);

Given the correct stream ID, the object may be restored using a function of the form:

object.RestoreL(store,streamId)

where store is a reference or pointer to a store.

The function names StoreL() and RestoreL() are conventional for this purpose.

The following diagram shows the idea of stream networks:

 \ No newline at end of file