No. Serialization is used whenever you want to preserve the state of an
object and/or transmit it across some type of boundary.
Writing the information to a file is one way to preserve the information and
you can definitely serialize for this reason. You might also want to
serialize and object before sending it across the internet such as a
webservice. Or you have out-of-process COM component (ServicedCompon ents)
which require that all passed information be serialized. Or, you can send
the data to a remote machine to be reconstructed and executed.
A recently project that I developed was a component that serialized an
object and encrypted it which was then saved to the registry.
"Patrick De Ridder" <ngmail@freeler .nl> wrote in message
news:8aemiv8g6g m8c5p6k3fcsb2ph ccvi4ksa3@4ax.c om...[color=blue]
> Am I right in assuming that serialization is only used when creating a
> sequentially written file?
> --
> Patrick De Ridder
> ngmail@freeler. nl
>[/color]
No. Serialization is used whenever you want to preserve the state of an
object and/or transmit it across some type of boundary.
Writing the information to a file is one way to preserve the information and
you can definitely serialize for this reason. You might also want to
serialize and object before sending it across the internet such as a
webservice. Or you have out-of-process COM component (ServicedCompon ents)
which require that all passed information be serialized. Or, you can send
the data to a remote machine to be reconstructed and executed.
A recently project that I developed was a component that serialized an
object and encrypted it which was then saved to the registry.
"Patrick De Ridder" <ngmail@freeler .nl> wrote in message
news:8aemiv8g6g m8c5p6k3fcsb2ph ccvi4ksa3@4ax.c om...[color=blue]
> Am I right in assuming that serialization is only used when creating a
> sequentially written file?
> --
> Patrick De Ridder
> ngmail@freeler. nl
>[/color]
On Sat, 2 Aug 2003 03:27:56 -0700, "Peter Rilling"
<peter@nospam.r illing.net> wrote:
[color=blue]
>No. Serialization is used whenever you want to preserve the state of an
>object and/or transmit it across some type of boundary.[/color]
On Sat, 2 Aug 2003 03:27:56 -0700, "Peter Rilling"
<peter@nospam.r illing.net> wrote:
[color=blue]
>No. Serialization is used whenever you want to preserve the state of an
>object and/or transmit it across some type of boundary.[/color]
Serialization is also useful to clone objects (implement the IClonable
interface). To support Cut & Paste and Drag & Drop. Also you can use
Serialization to store objects to a relational database as well.
The following 3 part MSDN Magazine column on Serialization, provides a
number of uses for serialization and how to implement them.
Find official documentation, practical know-how, and expert guidance for builders working and troubleshooting in Microsoft products.
Hope this helps
Jay
"Patrick De Ridder" <ngmail@freeler .nl> wrote in message
news:8aemiv8g6g m8c5p6k3fcsb2ph ccvi4ksa3@4ax.c om...[color=blue]
> Am I right in assuming that serialization is only used when creating a
> sequentially written file?
> --
> Patrick De Ridder
> ngmail@freeler. nl
>[/color]
Serialization is also useful to clone objects (implement the IClonable
interface). To support Cut & Paste and Drag & Drop. Also you can use
Serialization to store objects to a relational database as well.
The following 3 part MSDN Magazine column on Serialization, provides a
number of uses for serialization and how to implement them.
Find official documentation, practical know-how, and expert guidance for builders working and troubleshooting in Microsoft products.
Hope this helps
Jay
"Patrick De Ridder" <ngmail@freeler .nl> wrote in message
news:8aemiv8g6g m8c5p6k3fcsb2ph ccvi4ksa3@4ax.c om...[color=blue]
> Am I right in assuming that serialization is only used when creating a
> sequentially written file?
> --
> Patrick De Ridder
> ngmail@freeler. nl
>[/color]
Comment