lloyd / connect-select Goto Github PK

What if selectors were provided in HTTP headers? So a request could include:

X-JSONSelect-Filter: .foo > .bar

and if a server is capable of filtering the response, he includes a response header:

X-JSONSelect-Filtered: true

If the server doesn't know what the frak you're talking about, he just ignores you.

One thing I really like about this arrangement is you can then build efficient generic support into client libraries. They can send the filter and if the server doesn't support filtering then they can do client side filtering. Thinking like a jquery plugin or extension might be a fun way to explore this notion.

I'm uncertain whether this would break popular cache implementations though, because content varies based on the contents of the URL and the X header. Content with the same URL has different cache-able output.