On Tue, May 22, 2012 at 12:27 PM, John Locke <[email protected]> wrote:
> Possible Index handler: > GET /rest/1.0/my_company/ar_transactions/?invoice_id=N499216 I had a thought about this one. Suppose we allow a by= field to specify a non-standard id key? In that case, your URL would look like GET /rest/1.0/my_company/ar_transactions/N499216?by=invnumber The desired result would then be to get a redirect to the the cannonical URL. I am thinking that this avoids issues like: GET /rest/1.0/my_company/customers/A1234/locations/billing?customers_by=meta_number&locations_by=location_class In that case instead you'd do: GET /rest/1.0/my_company/customers/A1234?by=meta_number Capture the redirect address then do [redirect_address]/locations/billing?by=location_class You could then either do a redirect and add the extension or pursue the redirect with the content type header. Note, by would only be valid where the field is a valid secondary key. The modules would be responsible for enforcing this. Best Wishes, Chris Travers ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Ledger-smb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
