Return-Path: MIME-Version: 1.0 In-Reply-To: References: <1323703867-20577-1-git-send-email-bulislaw@linux.com> <1323703867-20577-4-git-send-email-bulislaw@linux.com> <20111215115009.GB8056@x220> <20111215121700.GA10535@x220> Date: Wed, 6 Jun 2012 11:14:36 +0300 Message-ID: Subject: Re: [PATCH obexd 4/4] Add support for PullMessagesListing in MAP client From: Luiz Augusto von Dentz To: Bartosz Szatkowski Cc: linux-bluetooth@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Bartosz, On Thu, Dec 15, 2011 at 2:45 PM, Bartosz Szatkowski wrote: >> >> So the plan is to return something else than the raw XML that MAP >> provides? In that case I don't think it's necessary to hold on to the >> exact spec naming of these functions. E.g. GetMessages or GetMessageList >> might make more sense in the case that you return a pre-parsed >> list/structure of some kind. >> >> Johan > > We planned to return dict {field: value}. Generally I don't care much > about this name - we can go with GetMessageListing, as I seem to use > both forms without noticing it anyway. Are there still plans to continue this work? I would like to change this method to return a dictionary like we do for pbap and perhaps unify this in a single listing so we do folder + messages. -- Luiz Augusto von Dentz