3rd party downloaded flag

Question

Is there a way to prevent this from being set?
I see Bug 614422 - Add ability to peek and not set third-party downloaded
is marked as complete for 8.0.3, but no details....

Answer 1

The mark download happens when we return the id's not
when the attachment data is returned.
For example:
You call getItemsRequest, getItemRequest,
getQuickMessages, readCursorRequet etc.
You have "default message attachments" in the view.
We will mark the item as read / opened / third-party
downloaded.
We return the item in the response.
You then call getAttachmentRequest (or stream) to
read the attachment data.
You call getItemsRequest, etc.
You have "default message peek attachments" in
the view.
We will mark the item as third-party downloaded.
We return the item in the response.
You will then call getAttachmentRequest (or stream
the attachment).
You call getItemsRequest, etc.
You have "default message peek noDownload attachments"
in the view.
You have signed in with a trusted app name and key.
The item is NOT marked read / opened / third-party
downloaded.
We return the item in the response.
You then call getAttachmentRequest (or stream the
attachment).
Does that make sense?
Preston
>>> On Monday, May 16, 2011 at 8:56 AM, Michael Bell<[email protected]>
wrote:
> On 5/16/2011 4:04 AM, Preston Stephenson wrote:
>> You can prevent the third‑party download bit from being set.
>> You login with a trusted app name and key.
>> You pass "noDownload" in the view when you get items.
>> For example, you could pass:
>> "default message peek attachments noDownload"
>> in the view.
>>
>> The fix is in 8.0.2 HP1 and later.(Any build greater than 90923.)
>>
>> Let me know if you have further questions.
>>
>> Preston
>>
>>>>> On Friday, May 13, 2011 at 1:26 AM, Michael Bell<[email protected]>
>> wrote:
>>> Is there a way to prevent this from being set?
>>>
>>> I see Bug 614422 ‑ Add ability to peek and not set third‑party
>> downloaded
>>>
>>> is marked as complete for 8.0.3, but no details....
> does that work for attachments too via the http streaming? Or do they
> not activate the flag?