|
|
I've never found this documented anywhere but from my experience there seems
to be some limit at 512 items with webdav replication you might want to look
at using the Range header to limit the size of the manifest to under 500
items see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wss/wss/_esdk_davrepl_range_header.asp?frame=true
Cheers
Glen
"Corey" <corey_farrell@xxxxxxxxxxxxx> wrote in message
news:I5HXg.6468$NE6.210@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> I'm trying to use WebDAV replication as described at:
> msdn.microsoft.com/library/default.asp?url=/library/en-us/e2k3/e2k3/_esdk_davrepl_replication_tasks.asp">http://msdn.microsoft.com/library/default.asp?url=/library/en-us/e2k3/e2k3/_esdk_davrepl_replication_tasks.asp
>
> It's working good, only problem I have is when I should fetch an updated
> manifest, when do I need to include a list of resourcetags? Testing with
> my own mailbox, I found that when I try replicating my Sent Items for the
> first time, it returns 512 out of 700 items. I then have to include the
> resourcetags list to replicate the remaining items - simply sending
> another request with the collblob that I received returns an error.
>
> How do I determine when sending the resourcetags list is required, and how
> do I tell if a response to a replication request is a complete list? My
> current work-around is to resend the request including resourcetags from
> the previous request until I receive an empty response, but there has to
> be a better way.
>
> My last question is if there are 2000 changes in a folder, what would I
> use for the resourcetags of request 3? Normally for request 2 I send the
> resource tags from response 1. For subsequent requests, do I keep
> replacing the resourcetags with the most recent responses, or do I need to
> keep adding to the list until I receive no responses?
>
> Thank you in advance!
> Corey
>
|
|