I think the challenge is deeper. All actions in the REST API contain
parsing code to bridge between the transport-style encoded form and
Java. Imagine a non-REST API added to ES. It would have to re-implement
all parsing code in the REST action classes.
Making this reusable would mean to refactor all the protocol parsing
code and reduce the REST API classes to a mininum.
Jörg
Am 27.06.13 08:27, schrieb Dawid Weiss:
Thanks for the hints, Martijn.
I think the parseSearchRequest method can be made protected.
For me it'd have to be public -- I don't want to subclass, I want to
keep my stuff separate and just delegate parsing of a fragment of my
request that I know is a search request. It'd be nice if it could be
made reusable I guess.Dawid
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.