overwrite a serialized object

[Lee Crabtree]

I'm serializing an object into a file in XML. After the object is
serialized, some other relevant data is written into the file. The rest
of the data winds up being very large most of the time.

Is there a way to re-serialize the object over itself? Here's a quick
example:

Say I have this:

<?xml version="1.0" encoding="utf-8"?>

<fileroot>

<SerializedObject>
<intParam>6</intParam>
<doubleParam>4.68</doubleParam>
</SerializedObject>

<otherData>blarg</otherData>

</fileroot>

Is it possible to replace the SerializedObject without disrupting the
rest of the data?

Thanks,

Lee Crabtree

[Chakravarthy]

Correct me ... if i'm not mistaken, all you want is, remove the
SerializedObject node and append new node in that place?

Yes it is possible... ping here, for more...
--
Every thing is perfect, as long as you share!!!
"Lee Crabtree" wrote:

I'm serializing an object into a file in XML. After the object is
serialized, some other relevant data is written into the file. The rest
of the data winds up being very large most of the time.

Is there a way to re-serialize the object over itself? Here's a quick
example:

Say I have this:

<?xml version="1.0" encoding="utf-8"?>

<fileroot>

<SerializedObject>
<intParam>6</intParam>
<doubleParam>4.68</doubleParam>
</SerializedObject>

<otherData>blarg</otherData>

</fileroot>

Is it possible to replace the SerializedObject without disrupting the
rest of the data?

Thanks,

Lee Crabtree

[Lee Crabtree]

That's right. What I've tried has worked as long as what is being
appended is the same size as what's being overwritten. Otherwise,
excess garbage sits on the end, or I overwrite data beyond the
serialized object.

Lee

Chakravarthy wrote:

Correct me ... if i'm not mistaken, all you want is, remove the
SerializedObject node and append new node in that place?

Yes it is possible... ping here, for more...

[Chakravarthy]

What is the mechanism did you use to append the data to XML elements?
Secondly, there is no restriction about the size that matters while appending
or deleting...

Post the code, to help you better
--
Every thing is perfect, as long as you share!!!
"Lee Crabtree" wrote:

That's right. What I've tried has worked as long as what is being
appended is the same size as what's being overwritten. Otherwise,
excess garbage sits on the end, or I overwrite data beyond the
serialized object.

Lee

Chakravarthy wrote:

Correct me ... if i'm not mistaken, all you want is, remove the
SerializedObject node and append new node in that place?

Yes it is possible... ping here, for more...

[Lee Crabtree]

Well, I couldn't use the XmlDocument class, as it is a full cache tree
of the file. A file of several hundred megs is prohibitively large and
slow, and I can't afford that kind of pain. So I was using
XmlTextReaders and XmlTextWriters to change the data and write it back.
But, as I said, data was either overwritten or underwritten.

Lee

Chakravarthy wrote:

What is the mechanism did you use to append the data to XML elements?
Secondly, there is no restriction about the size that matters while appending
or deleting...

Post the code, to help you better

[Morantex]

Hi

I have just read your post about mpdifying a serialized object.

I want to draw your attention to a new technology we have recently made available in beta.

Persistore is the first managed class library for .NET 2 that provides access to persistent shared memory.

Now I am not 100% clear on your situation, but there may be some use in taking Persistore for a "test drive". One thing it supports is the ability to call ReadObject, WriteObject, UpdateObject and DeleteObject on [Serializable] .NET objects and supports multiple versions of an object.

These objects are serialized into shared memory (and hence they are persistent) this is a fast operation because there is no disk IO involved.

Persistore basically implements its own shared memory file system and allows you to create directories in which to store data. Because of its nature it is used to store variables and arrays as well as files (known as SharedStreams) and offers services unavailable in other products.

Get the beta from our site: http://www.morantex.com/Persistore.aspx and do not hesitate to contact me with questions or requests, we are working on the next beta and keen to address any real-world customer needs.


Regards
Hugh

[e-mail]

Well, I couldn't use the XmlDocument class, as it is a full cache tree
of the file. A file of several hundred megs is prohibitively large and
slow, and I can't afford that kind of pain. So I was using
XmlTextReaders and XmlTextWriters to change the data and write it back.
But, as I said, data was either overwritten or underwritten.

Lee

Chakravarthy wrote:[color=blue]
> What is the mechanism did you use to append the data to XML elements?
> Secondly, there is no restriction about the size that matters while appending
> or deleting...
>
> Post the code, to help you better[/color]

[Chakravarthy]

Ken Getz, is another MVP and one of his webcast will help you in detail about
how to handle the nodes insertion and deletion. You can reach his website for
this, i would suggest you to spend some time to listen what he says and go
ahead with your work.

At this link, http://www.mcwtech.com/2004/webcasts/ you can find all his
contributions towards the dev community, among which you also see the XML DOM
topic with the title, "Using the XML DOM in .NET Applications"

Dont think that instead of listening to him, you can do R&D over internet
.... this will be definitly helpful to you...

--
Every thing is perfect, as long as you share!!!
"Lee Crabtree" wrote:

Well, I couldn't use the XmlDocument class, as it is a full cache tree
of the file. A file of several hundred megs is prohibitively large and
slow, and I can't afford that kind of pain. So I was using
XmlTextReaders and XmlTextWriters to change the data and write it back.
But, as I said, data was either overwritten or underwritten.

Lee

Chakravarthy wrote:

What is the mechanism did you use to append the data to XML elements?
Secondly, there is no restriction about the size that matters while appending
or deleting...

Post the code, to help you better