20bf1f632f
* The existing IMAP search code is well-known to be primitive and largely broken. In particular, it fails with any non-ASCII character and with a variety of symbols (e.g. quotes, slashes, etc.) Basically, it's an accident waiting to happen, returning empty data sets even when the query might reasonably be expected (or known) to return valid data. * The current CL uses the IMAP literal string format to represent the query text; this string can be sent either in ascii or in UTF-8, and since it is sent as an octet (byte) count followed by 8-bit data, it also solves any quoting issues that might come up. So, we kill two birds with one stone. * The bug in question was punted to a subsequent MR; however, I think it would be a mistake to ship the code without this CL, which has been tested against the three common IMAP servers that we aim to support. Bug: 4690713 Change-Id: Iaa542bfc56737871f3cbc9c83f0e768415a7f2b6 |
||
---|---|---|
assets | ||
emailcommon | ||
res | ||
src/com | ||
tests | ||
.classpath | ||
.project | ||
Android.mk | ||
AndroidManifest.xml | ||
CleanSpec.mk | ||
MODULE_LICENSE_APACHE2 | ||
NOTICE | ||
proguard.flags | ||
remove-exchange-support.sh |