Re:Limitations of the GET method in HTTP
by evincarofautumn on Tuesday March 03, 2015 @02:05AM
(#9136468)
That’s technically true, but performance-wise I’m not realistically going to submit two separate requests for what is semantically one action. On the other hand, it makes the query resource reusable for saved searches, and for showing search history.
[ Parent
| on HN ]
Re:Limitations of the GET method in HTTP
by justincormack on Tuesday March 03, 2015 @03:27AM
(#9136655)
It is not much different from a prepared statement or a stored query, indeed it can even be parameterized. With keepalive two requests is not so bad.
Re:Limitations of the GET method in HTTP
by madeofpalk on Tuesday March 03, 2015 @05:55AM
(#9137073)
And then you need to store the queries in a database. Make sure we flush them out 'some time'. What happens when a client tries to use a flushed query? Something that previously works now no longer does.
Or, lets just use POST.