Re: dynamic containers issue

On Tue, 2010-05-18 at 19:16 +0300, Zeeshan Ali (Khattak) wrote:
> > Now, it is there, but still I need to cope with the non-paging browsing.
> > Which fits nice for static content, but not so nice for content like
> > Youtube
>   Since non-paged browsing is a specific form of paged-browsing, I
> don't see why it should be a problem for you.The client can ask for
> ALL children of a container even if you only provide paged-browsing
> APIs so you'll have to handle that anyways.

Yes, sure. And I'm handling it. But actually if client queries *all*
elements in a single page, then it is her problem: she never ever should
get all elements in a single page. 

> >. And of course, with the ItemCount and ContainerCount.
>   Dude, they are optional for a few weeks now and I didn't say we
> should make them mandatory in this discussion, we are only talking of
> ChildCount property now.

So, maybe I was confusing but, is there 3 count-keys then: ItemCount,
ContainerCount and ChildCount, being the 2 former optional and later

> > So, you're meaning that not having a ItemCount and ContainerCount in
> > youtube, for instance, is a bug in the service, right? Well, I'm afraid
> > most of web services have that bug :)
>   No I mean providing means to figure out 'ChildCount'. Tracker guys
> have thought of  that (you can request the count of results of a
> query) and UPnP has thought of that so its really a bug in the
> services, doesn't matter if  all such services do not provide such
> APIs.

Really, I'm sorry, but I don't see yet why ChildCount should be a
compulsory key... Sure, it can be an useful key, but still I don't get
it why compulsory.


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