Find answers, ask questions, and connect with our
community around the world.

Forums Forums Web Design Would allowing multiple querystrings in URLs allow more scalable APIs?

  • Would allowing multiple querystrings in URLs allow more scalable APIs?

    updated 2 years, 4 months ago 0 Member · 1 Post
  • Maverick

    Member
    September 11, 2019 at 11:02 pm

    Imagine if could GET `https://bar.mywebsite.foo/gadgets?name=foo&age>=100/gizmo/components?type=types.gizmo.component.square`. I know it’s ugly and not legal URI syntax, but this could cut N GETS into one, where, as one possibility, the server could compile the path into the separate requests (if necessary). Then again, I guess this transformation could happen client-side. It seems like repeated filtering is always involved in getting some desired resource; it would be great to get this with one request. Perhaps that newcomer GraphQL addresses this by design. Often I wonder if the best HTTP API would involve the remote execution of some non-turing-complete query-language guaranteed to terminate. Just select, filter, basic “joins”, etc. I’ve heard about OData – but does it allow recursing “inline” like in the example URI I gave? – by hq overview kizerkizer – –

Viewing 1 of 1 replies
Reply to: Maverick
Your information:

Cancel
Original Post
0 of 0 posts June 2018
Now