SCope
SCope copied to clipboard
Replace gRPC as client protocol with HTTP "REST" style API
This is a tracking issue:
- [x] Set up FastAPI #286
- [x] Set up SQLAlchemy and database #321
- [x] Client authentication flow (through ORCiD) #322
The way to do this is to implement a duplicated API and either run them both in parallel or have a feature flag
I don't really get the duplicated API... Could you elaborate please ?
Could you elaborate please ?
I mean keep the gRPC API while implementing the HTTP API. Then the client can be gradually moved to the new API