[
"appModelVersion:2",
"accessTokenVersion:1",
"availableToOtherTenants:true",
"supportsConvergence:true",
"emailAddress:...@gmail.com"
]
JSON, motherfucker, do you speak it?
[
"appModelVersion:2",
"accessTokenVersion:1",
"availableToOtherTenants:true",
"supportsConvergence:true",
"emailAddress:...@gmail.com"
]
JSON, motherfucker, do you speak it?
Разработчики IMAP-сервера на hotmail (outlook) -- просто эталонные индусы:
- Время выполнения почти любого FETCH-запроса по контенту письма, будь то envelope (стандартные заголовки), все письмо, только subject или конкретная mime-part -- пропорционально размеру сообщения. На письмах в десятки МБ запрос тупит секунды.
- Параллельный логин иногда выдает прекрасное
OK Authentication encountered server error. Try again later.
OK, Карл! После этого след. команда отваливается с ошибкой "неверное состояние".
SMTP-сервер тоже прекрасен -- заменяет у письма Message-ID.
The application Microsoft Error Reporting Tool quit unexpectedly. ... Click Report to ... send a report to Apple.
мимими 1:
The "best" example of this maintainability problem could be found in the old implementation of the printf family of functions. The CRT provides 142 different variations of printf, but most of the behavior is the same for all of the functions, so there are a set of common implementation functions that do the bulk of the work. These common implementation functions were all defined in output.c in the CRT sources(1). This 2,696 line file had 223 conditionally compiled regions of code (#ifdef, #else, etc.), over half of which were in a single 1,400 line function. This file was compiled 12 different ways to generate all of the common implementation functions.
мимими 2:
We have converted most of the CRT sources to compile as C++, enabling us to replace many ugly C idioms with simpler and more advanced C++ constructs. The publicly callable functions are still declared as C functions, of course (extern "C" in C++), so they can still be called from C. But internally we now take full advantage of the C++ language and its many useful features.
мимими 3:
Before this refactoring, the sprintf functions, which write formatted data to a character buffer, were implemented by wrapping the result buffer in a temporary FILE object and then deferring to the equivalent fprintf function.