On 10/05/11 23:17, elij wrote:
On Tue, May 10, 2011 at 2:04 PM, kachelaqa<[email protected]> wrote:
i think all the available information should be included.
I disagree with such a broad statement as this.
By that logic all comments should be included too, which I also think
would be a bad idea.
Perhaps you meant 'all package table data', which (while I would still
disagree with in this instance) would be more reasonable.
yes, that is what i meant - just the package table data.
I think it makes sense to include data that is useful, while excluding
data that is either unused or of very little use *in the context of
the api*. In general, I am a minimalist.
i agree that submitter is by far the least useful item of information.
Also keep in mind traffic volume, and note that additional data points
means more [bytes] traffic sent down the pipe to end users. The rpc is
a fairly high volume interface, as Dan has previously outlined based
on server logs. This point probably isn't such a large concern for the
small amount of that this patch adds to the result set, but something
like including comments would be very much at odds with the api design
and goals. I include this point for completeness only.
this is actually the main aim of my patch. currently, it is necessary to
make three separate queries to get all the information about a package.
one for the rpc data, one to scrape 'maintainer', 'last updated', etc
from the package details page, and one for the pkgbuild. the second
query can be eliminated altogether if all the package table data can be
obtained from the rpc query.
As an aside, I would argue that the submitter field should be removed
from the aur altogether, as the current maintainer is the only really
useful datapoint of the two.
i have no problem with this, at all.
maybe i should revise my patch to add only the 'last updated' and 'first
submitted' data. it would certainly make it a lot simpler!
