On Tue, Apr 12, 2011 at 12:15:49AM -0500, Dan McGee wrote:
The majority of real world info requests [1] come in hefty batches. We
would be better served to handle these in one request rather than
multiple by allowing AUR clients to send multiple arguments.
This enables things like this to
On Sat, Apr 16, 2011 at 11:07 AM, Lukas Fleischer
archli...@cryptocrack.de wrote:
On Tue, Apr 12, 2011 at 12:15:49AM -0500, Dan McGee wrote:
The majority of real world info requests [1] come in hefty batches. We
would be better served to handle these in one request rather than
multiple by
We seem to have a fundamentally different conception here. What you
call validate I consider, simply sorting. You even called it
sorting in your first paragraph. There is no validation of information
happening at all. Calling this algorithm validating lends it a false
sense of gravity. It is no
On Wed, Apr 13, 2011 at 08:11:18AM -0500, Dan McGee wrote:
I am merely suggesting that the server sort the results for the RPC
user. This makes things easier and more intuitive for the user. In the
process of querying package info as a whole, you are going to have to
associate query words
On Mon, Apr 11, 2011 at 10:15 PM, Dan McGee d...@archlinux.org wrote:
[1] Rough data from April 11, 2011, with a total hit count of 1,109,163:
12 /login.php
13 /rpc.php?type=sarch
15 /rpc.php?type=msearch
16 /pingserver.php
16 /rpc.php
22 /logout.php
163
On Mon, Apr 11, 2011 at 10:15 PM, Dan McGee d...@archlinux.org wrote:
The majority of real world info requests [1] come in hefty batches. We
would be better served to handle these in one request rather than
multiple by allowing AUR clients to send multiple arguments.
This enables things like
On Tue, Apr 12, 2011 at 1:04 AM, elij elij...@gmail.com wrote:
On Mon, Apr 11, 2011 at 10:15 PM, Dan McGee d...@archlinux.org wrote:
The majority of real world info requests [1] come in hefty batches. We
would be better served to handle these in one request rather than
multiple by allowing AUR
On Tue, 12 Apr 2011 00:15:49 -0500
Dan McGee d...@archlinux.org wrote:
The majority of real world info requests [1] come in hefty batches.
We would be better served to handle these in one request rather than
multiple by allowing AUR clients to send multiple arguments.
Hi, similarly, for AUR
On Tue, Apr 12, 2011 at 6:05 AM, Tuxce tuxce@gmail.com wrote:
On Tue, 12 Apr 2011 00:15:49 -0500
Dan McGee d...@archlinux.org wrote:
The majority of real world info requests [1] come in hefty batches.
We would be better served to handle these in one request rather than
multiple by
On Tue, Apr 12, 2011 at 09:05:05AM -0500, Dan McGee wrote:
On Tue, Apr 12, 2011 at 8:52 AM, Justin Davis jrc...@gmail.com wrote:
Tuxce submitted a similiar patch awhile back:
http://mailman.archlinux.org/pipermail/aur-dev/2010-November/001349.html
The patch file isn't on the mailing list
On Tue, Apr 12, 2011 at 01:05:28PM +0200, Tuxce wrote:
From d7d06859ddc9425930e586a0685f09f9798dfddc Mon Sep 17 00:00:00 2001
From: tuxce tuxce@gmail.com
Date: Tue, 12 Apr 2011 12:42:30 +0200
Subject: [PATCH] rpc: unify methods return.
Include maintainer in info and search method.
You
The majority of real world info requests [1] come in hefty batches. We
would be better served to handle these in one request rather than
multiple by allowing AUR clients to send multiple arguments.
This enables things like this to work:
12 matches
Mail list logo
