Following REST principles, I would want to create a GET method for my API that make a search using some criteria and return the results to the client. The problem is that the criteria can have up to 14 parameters, one of them is a list of complex objects, so...
I don't even know if it possible to encode/decode these complex objects to/from url parameters.
I didn't calculate how long the url could get but I'm sure it will be large enough and maybe reach the url length limit?
Also, the search should show the results in "real time", I mean, every time the user changes something from the search form he should be able to see the new results without pressing any "search" button.
Could you clarify me these points and what would be your advice to create a restful search method with a lot of parameters?
update: now that I have more experience, I've realized that having to do a search method with A LOT of parameters is actually something that designates bad design and bad requirements, and @Neil answer has the point. So my advice is don't feel "bad" about not being able to make it RESTfu and do what you can within the scope. Nevertheless, the @Laiv answer is still good for less extreme cases, so take it into account too.