[aur-dev] [PATCH 4/4] rpc: allow multiple args on info query

[Justin Davis]

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 but I have it in my inbox still.

I remember because I added a few patches to it. Are packages returned
in the same order that their names are given? I remember this was a
problem with Tuxce's patch (which I patched). What about queries that
do not match any results? Will the array of results be smaller than
the number of queries? From reading the first patch in this thread, it
seems that if IDs and names are used as query args their order is lost
because they are split into separate arrays. When using WHERE IN do
the results match the order of query arguments? Because we are
returning a JSON array, order is important to associate results with
our query.

I like using spaces better and don't see how they could have a
different meaning in msearch. It seems like spaces would have a
similar meaning when used in args to msearch (splits keywords for
msearch, names/ids for info). It's not really a big deal though... I
can live with the ugliness...

Just playing the role of devil's advocate here. Yay RPC overhaul,
thanks Dan! Yay maintainer names in RPC results!

PS I wonder how many of those rpc.php?type=info queries are from keenerd? hehe!

-- 
-Justin