Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754766Ab0HKQSZ (ORCPT ); Wed, 11 Aug 2010 12:18:25 -0400 Received: from mail-ew0-f46.google.com ([209.85.215.46]:50747 "EHLO mail-ew0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753221Ab0HKQSX (ORCPT ); Wed, 11 Aug 2010 12:18:23 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=fPkmnTqAdYidm8Z+lxTQstkgYw2k1nMXMcakiAzEopvFI0P04PgoguZq0PLyQSN4WB QS9AOULePik0ZwLqdUt0A0bABFfQhlLOqlL1Ai1/GRkObFzLjwGWB6DTb5QgjvV8+MwU ghWM2LPNWOcRNY2Ya/E+Z7lNWdkY1VjCaA32w= MIME-Version: 1.0 In-Reply-To: <1281542305.5107.11.camel@localhost> References: <4C5F9B25.8080401@st.com> <4C624AE1.30504@st.com> <4C62C5BD.3020808@mnsu.edu> <1281542305.5107.11.camel@localhost> From: Avery Pennarun Date: Wed, 11 Aug 2010 12:18:02 -0400 Message-ID: Subject: Re: Query: Patches break with Microsoft exchange server. To: David Woodhouse Cc: Jeffrey Hundstad , viresh kumar , Felipe Contreras , "git@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "Justin P. Mattock" , =?ISO-8859-1?Q?Uwe_Kleine=2DK=F6nig?= , Valeo de Vries , Linus Walleij , Matti Aarnio , mihai.dontu@gmail.com, richardcochran@gmail.com, "Gadiyar, Anand" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1082 Lines: 24 On Wed, Aug 11, 2010 at 11:58 AM, David Woodhouse wrote: > In Evolution we have a workaround -- we don't just stop when we get to > the reported RFC822.SIZE; we continue fetching more chunks until the > server actually stops giving us any more. It's not as efficient (because > we fall back to having only one more chunk outstanding at a time rather > than the normal three in parallel), but at least it works around this > brokenness of Exchange. > > http://git.gnome.org/browse/evolution-data-server/commit/?id=9714c064 Out of curiosity, why fall back to one chunk at a time? It seems to me that IMAP should be able to still support multiple outstanding requests in that case, but you'd just get errors on the latter chunks. It is just that there was no point optimizing the workaround case? Have fun, Avery -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/