0c509ec05f8a67664f158a3fe78513afbb0309c4 |
|
11-Oct-2011 |
Marc Blank <mblank@google.com> |
Don't spam the Email app with attachment load progress * I observe that the read() can return with as little as 100 bytes read; this can lead to lots of spamming via the binder interface. * Limit callbacks based on both percentage read and bytes read Bug: 5433427 Change-Id: I25a20279c065bfc1b22c5e2633fc465109cca495
/packages/apps/Exchange/src/com/android/exchange/adapter/AttachmentLoader.java
|
591ed9c507ec77af458bcc321c9109dee5b34739 |
|
04-Oct-2011 |
Marc Blank <mblank@google.com> |
Fix regression with attachment loading progress * Oops! Bug: 5375620 Change-Id: Ie890756c4c5d9fd970670007dcb0f38825eba23b
/packages/apps/Exchange/src/com/android/exchange/adapter/AttachmentLoader.java
|
5870214d6c4991dd0a863bcd097860ddd896cab6 |
|
21-Sep-2011 |
Marc Blank <mblank@google.com> |
Remove illegal characters from EAS 2.5 attachment file names * For some reason, EAS 2.5 sends us partially encoded file names, which we use to specify attachments to be loaded. * It turns out that these file names aren't properly encoded for EAS's use in the GetAttachment command; some additional characters must be escaped using %nn. * We now check for EAS 2.5 and escape illegal characters Bug: 5341416 Change-Id: Ie112359e139581c8ae31e40869b2fa0e568d7f65
/packages/apps/Exchange/src/com/android/exchange/adapter/AttachmentLoader.java
|
abdfa52b4260111c706edc92c5405e9eb4723554 |
|
07-Sep-2011 |
Marc Blank <mblank@google.com> |
Allow attachment reading past expected file length * It appears that (at least with message/rfc822 type attachments), the actual data length can significantly exceed the expected length * It was probably always dangerous to break; out of the read loop anyway Bug: 5265760 Change-Id: I055636709088717f6b6b1959bcc33d8e24574bb7
/packages/apps/Exchange/src/com/android/exchange/adapter/AttachmentLoader.java
|
498c903e02ef1b150d6dbd3a01d35839026db264 |
|
10-Jun-2011 |
Ben Komalo <benkomalo@google.com> |
Move EasResponse to top level class. All behavior unmodified. This prepares the way for some additional error codes (that aren't necessarily HTTP error codes, since no connection can even be made) that will be put on the EasResponse itself. Change-Id: I1ba3b212dc63fb2f10a6462466e8fe62409b87e9
/packages/apps/Exchange/src/com/android/exchange/adapter/AttachmentLoader.java
|
bb12673b0aa36ff0751ddcffe02223c6100f424e |
|
12-May-2011 |
Marc Blank <mblank@google.com> |
Add support for EAS 14.1 attachment loading * Move all attachment handling code out of EasSyncService and into new AttachmentLoader class * A bit of cleanup to existing attachment code Change-Id: I4f6a7950b1318f838413b83d6cfae31f0467e8d1
/packages/apps/Exchange/src/com/android/exchange/adapter/AttachmentLoader.java
|