Large child object count causes update failure

esaulsberry posted on Friday, July 17, 2009

I'm working on a Silverlight project using CSLA 3.7.0. On a form bound to a typical root-childist-child pattern, with a few child objects it works fine. If I load a thousand child records the update fails here:

public Csla.WcfPortal.WcfResponse EndUpdate(System.IAsyncResult result) {
object[] _args = new object[0];
Csla.WcfPortal.WcfResponse _result = ((Csla.WcfPortal.WcfResponse)(base.EndInvoke("Update", _args, result)));

With a "Not Found" error message.

The client side config looks like this:
maxBufferSize="2147483647"
maxReceivedMessageSize="2147483647">

And the server side...
maxReceivedMessageSize="2147483647">
maxBytesPerRead="2147483647"
maxArrayLength="2147483647"
maxStringContentLength="2147483647"
maxDepth="4096"/>

RockfordLhotka replied on Friday, July 17, 2009

Are you using compression? You really must use compression.

The XML generated by the DataContractSerializer gets very large very fast, but it compresses very effectively (XML is so terribly verbose, but it is repetative, so compression is effective).

esaulsberry replied on Friday, July 17, 2009

RockfordLhotka:

Are you using compression? You really must use compression.

The XML generated by the DataContractSerializer gets very large very fast, but it compresses very effectively (XML is so terribly verbose, but it is repetative, so compression is effective).

No. Any guidance on how to "turn it on"?

RockfordLhotka replied on Friday, July 17, 2009

Do you have the CSLA .NET for Silverlight video series? I walk through setting this up in some detail in the videos.

You can also look at the InventoryDemo sample to see how it is set up there, and there’s an article in the FAQ

http://www.lhotka.net/cslanet/faq/SilverlightDataPortalCompression.ashx

Rocky

esaulsberry replied on Friday, July 17, 2009

RockfordLhotka:

Do you have the CSLA .NET for Silverlight video series?

Man, if I could squeeze $300 out of them (well $500 anyway), I wouldn't be developing on a P4 with 2GB ram.

I'll take a look at the examples though.

Elton

esaulsberry replied on Friday, July 17, 2009

Compression seems to have healed it, although some sort of paging mechanism is probably desirable in the long run.

Any thoughts on this one?

http://forums.lhotka.net/forums/thread/34817.aspx