2020-02-13 11:23 AEST by Arthur Barrett - For many reasons (Jira, Bugzilla, etc.) we need to be able to do REST within CVSNT.

It probably makes sense to have this exposed publicly via the CVSAPI so any plugin can use it.

It needs to be cross platoform and it can't depend on C++ 11 features, so that rules out things like 
cpprestsdk:
https://github.com/Microsoft/cpprestsdk

So that probably means linking to openssl (which we already do for the sserver protocol, but it makes it a 
core dependency - though in theory we don't need it until the API is actually called (if it's set to load run-time 
- I'm not quite sure how to do this on Linux).

We also therefore probably need to link to jansson, so that's another dependency...

So maybe putting this all in CVSAPI is not so clever.  Maybe we need a separate library? SUITEAPI?

Or we can put all this into CVSMANAGER and the plugins connect to CVSMANAGER to perform these tasks - 
CVSMANAGER can maintain a single connection?  But that makes little sense for RESTful services.

I wonder if EVSCM already has something?  Lots of HTTP stuff in there already... I should at least look at it as 
part of the investigation...