5.1 Reading Target Digest

In a first step, the synchronization engine obtains the synchronization digest from the target application:

GET /sdata/myApp2/myContract/-/accounts/$syncDigest HTTP/1.1

The target application responds with an Atom entry like the following:

200 OK
Content-Type: application/atom+xml; type=entry

<entry xmlns="http://www.w3.org/2005/Atom">
  <id>http://www.example.com/sdata/myApp2/myContract/-/accounts/$syncDigest</id>
  <title>Synchronization digest</title>
  <updated>2008-03-31T13:46:45Z</updated>
  <link rel="self" type="application/atom+xml; type=entry" title="Refresh" 
        href="http://www.example.com/sdata/myApp2/myContract/-/accounts/$syncDigest" />
  <payload xmlns="http://schemas.sage.com/sdata/2008/1">
    <digest xmlns="http://schemas.sage.com/sdata/sync/2008/1">
      <origin>http://www.example.com/sdata/myApp1/myContract/-/accounts</origin>
      <digestEntry>
        <endpoint>http://www.example.com/sdata/myApp1/myContract/-/accounts</endpoint>
        <tick>5</tick>
        <stamp>2008-10-30T14:52:03.281Z</stamp>
        <conflictPriority>2</conflictPriority>
      </digestEntry>
      <digestEntry>
        <endpoint>http://www.example.com/sdata/myApp2/myContract/-/accounts</endpoint>
        <tick>11</tick>
        <stamp>2008-10-30T13:46:45Z</stamp>
        <conflictPriority>1</conflictPriority>
      </digestEntry>
      <digestEntry>
        <endpoint>http://www.example.com/sdata/sageApp3/test/-/accounts</endpoint>
        <tick>8</tick>
        <stamp>2008-10-30T12:40:25Z</stamp>
        <conflictPriority>3</conflictPriority>
      </digestEntry>
    </digest>
  </payload>
</entry>