On Thu, Nov 16, 2017 at 5:30 PM, Jeremy Audet <jau...@redhat.com> wrote: ...snip
> > Worse, let's say I'm a developer debugging an issue, and I want to find > every concentrated sprayflesh in the known world. Do I need to make several > thousand API calls? Both of these use cases are more elegantly solved by > allowing users to work directly with items, and by providing good filtering > support. This is based on my experience with some small old apps though, > and none of them went into production. Take it as you will. > > +1, we don't want to Torment our users. To spell it out, a flat structure enables use cases for filtering all objects, rather than the subset that is nested under a parent object. For example, a user could filter all importers by feed url, rather than filtering only the importers associated with a specified repository.
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
