On Wed, 2012-06-20 at 20:27 +0300, Gary Kotton wrote: > >> > >> Please let me know if you have any comments. > > The only issue is then we can't search by ip unless we invent a schema > > for nested resource searching. One of the reasons I was an advocate of a > > top level /ips resource. > I am not sure that I understand. I do not understand how the > configuration parameters affect the search. Can you please clarify. The > above proposal is changing the input from the user.
So to search for an ip we can currently do: GET /ports?ips=172.16.0.1 Since this would be an encapsulated resource (you cant get to it any other way), we'd have to document a hierarchy separator so something like: GET /ports?ips.ip_address=172.16.0.1 This just seams dirty to me, since I would expect ip then to not be a collection but to be a resource itself. Much better in my opinion would be: GET /ips?address=172.16.0.1 Since its a direct lookup on a resource. Happy Hacking! 7-11 -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
