recommended approach for large saves with ANDS

02-08-2009 2:37 PM |

Hi,

I'm using ADO.Net Data Services, and when a save happens that is greater then 65k it will fail, as I understand that is the default max size set on the IIS server.   When I present a datagrid to the user, they may update multiple rows and a save (MERGE) can result in a lot of data to be sent back.

The samples I've looked at don't seem to really address this, please point me to one if one exists.

I'm curious what others have done, do you save per entity/row when users move to another row (how do you catch this reliably?), or do you have routines that break up the save into smaller pieces, or...?

btw I've tried setting a flag on PropertyChanged, and in SelectionChanged checking and saving as necessary but I get a lot of false positives for screen refreshes etc., seems there should be a cleaner approach to this.

thanks,

- Larry

Re: recommended approach for large saves with ANDS

02-24-2009 12:35 PM |

Thanks for the feedback Ken.  Not quite the volume of responses I was hoping for but I guess folks are busy.