Re: dynamic containers issue

["Zeeshan Ali (Khattak)" <zeenix gmail com>]

Hi,

On Tue, May 18, 2010 at 7:34 PM, Juan A. Suarez Romero
<jasuarez igalia com> wrote:
> On Tue, 2010-05-18 at 19:21 +0300, Zeeshan Ali (Khattak) wrote:
>> 1. Thats just one usecase, this could also be used for UIs to tell the
>> user which container has how many items. At least I would love to see
>> that in UIs.
>
> Yes, and I'd like to see the other optional properties: album, artist,
> even an album art :). But it doesn't mean that it must be compulsory.

  Those only makes sense for some particular type of items. This
property makes sense for ALL types of containers.

>> 2. As i said in the first email, in case of UPnP I have no means of
>> telling the client that container's child count is unknown. I only
>> have an unsigned integer.
>
> I see.... I would say that it is a bug in uPnP :)

  Yes, if you think they should have thought about the limitations of
youtube APIs  in 2001, yes it's a bug. :)

  To summarize the discussion, if you are going to implement the
solution I proposed (or some variant of it) along with the limiting
child count you already have, there is no problem making this property
compulsory. OTOH if you are not going for that solution, I really want
to know how you are going to deal with the incremental browse issue I
mentioned.

-- 
Regards,

Zeeshan Ali (Khattak)
FSF member#5124