Hello pps, Monday, December 12, 2005, 3:56:46 AM, you wrote:
Certainly Serialization doesn't have anything to do with transmission specifically but, the same thing that makes it work in blobs, ie taking all the values and pointers in a class and converting them into a data unit, then converting them back into the the data structure when it's read back out, would also let you use it to transmit data over a TCP connection and re-create the class on the other side. Whether I'm "transmitting" to a disk file, database or TCP connection, in this case it works out to be the same thing. C p> Teg wrote: >> Hello John, >> >> You guys are both going off in you own directions and arguing >> something that's really an unimportant implementation detail. >> Serialization's a wonderful thing, if you need it. It's nothing more >> than a protocol for storing, saving, transmitting something in a >> format that can be re-constituted on the the other side by a reader. >> It's useful, if you need it and solves problems some implementations >> have. p> I'd like to correct you a little. Serialization has nothing to do with p> transmitting. Serialization is simply decompostion of some complex p> arbitrary data (a struct instance) into something simple (sequence of p> bytes, binary string, ...), and construction from bytes to complex data.
