Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

move to RESP instead of RESTful API #2

Open
alash3al opened this issue Dec 15, 2018 · 4 comments
Open

move to RESP instead of RESTful API #2

alash3al opened this issue Dec 15, 2018 · 4 comments
Assignees
@alash3al
Labels
enhancement New feature or request
Milestone
v1.1

Comments

@alash3al
Copy link
Owner

There is a plan to move away from REST service to RESP (redis protocol) using redcon, this will enable srchx to be faster than the current HTTP based implementation.
@alash3al alash3al added the enhancement New feature or request label Dec 15, 2018
@alash3al alash3al self-assigned this Dec 15, 2018
@alash3al alash3al added this to the v1.1 milestone Dec 15, 2018
@sandeepone
Copy link

How about GRPC?

@ghost
Copy link

ghost commented Jan 29, 2019

Should be quite easy to put a GRPC APi on top.

@fi0
Copy link

fi0 commented Aug 25, 2019

gRPC would be cool!

@winwisely99
Copy link

grpc badger and bleve
https://github.com/mosuka/blast

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alash3al alash3al

Labels
enhancement New feature or request
Projects
None yet
Milestone
v1.1
Development

No branches or pull requests
4 participants
@sandeepone @alash3al @fi0 @winwisely99