I agree matrix are more state oriented then query.
so, where we are at is:
thing
;thing=this ;thing=this|that ;min_thing=this
the only one I can see us improving is the last, but not extremely important if we can't.
Cheers, -Adrian
On Mon, Nov 16, 2009 at 11:36 AM, Ivan Meredith ivan@ivan.net.nz wrote:
2009/11/17 Adrian Cole adrian@jclouds.org:
good idea.. One thought: as opposed to supporting less than greater than, we could say we only support equals and at least.
That limits the association to 2 types, which we could (in a hackish way) encode using the two common request parameter types:
query is for squishy matrix is for must be
ex. ;arch=x86?mem=2?core=2
arch must be x86, but I can use anything with at least 2g memory and 2 cores
pros are that we do not need to invent something we'd need to encode, and don't need to parse parameter names.
cons is that the thing is a little weird
wdyt?
I personally think that just using matrix params for this is best. I have no real reason, i just see it as less complicated.
personally i see...
no arch = any ;arch=x86 ;arch=x86|x64