Re: [PATCH obexd 4/4] Add support for PullMessagesListing in MAP client

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Dec 15, 2011 at 1:17 PM, Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote:
> Hi Bartosz,
>
> On Thu, Dec 15, 2011, Bartosz Szatkowski wrote:
>> > The name should be GetMessageListing and not GetMessagesListing (the
>> > latter isn't really proper english). I went ahead and changed it through
>> > a separate patch since I didn't notice before having already applied
>> > your patch. Also, all this seems to be missing from the API
>> > documentation (doc/*). Please send a patch for that.
>>
>> The function name is "GetMessagesListing" in spec.
>> There is no doc as at the moment there is no apparams handling and no
>> xml parsing, so I'll send patch with doc when we reach full
>> functionality.
>
> 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.

-- 
Pozdrowienia - Cheers,
Bartosz Szatkowski
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux