Service abstraction

[wgifford]

Initial service abstraction

• defines abstract classes for service handlers
• defines huggingface service handler which supports huggingface specific conventions
• defines model-specific service handles (derived from above handlers) that enables model-specific features

[ssiegel95]

I'll have a look at this tomorrow @wgifford, thanks.

[wgifford]

To do items:

• Assess naming, adjust as needed.
• Standardize what is needed in tsfm_config.json. Identify minimum requirements, requirements for HuggingFaceHandler, etc.
• Do we still need a global confing.yaml? If not, remove. Keep for now.
• Allow pulling the tsfm_config.json from HF (just like normal configs).
• Resolve issue of model_id becoming the full path in the PredictionResult

[ssiegel95]

I would have expected to see an import of tsfm_service_handler here.

[wgifford]

We just need the base service handler -- it will be used to load the right handler class.

[ssiegel95]

Given that there's a fair amount of implementation on this object, is it really an "abstract" base class, it seems to be just a run of the mill base class.

[ssiegel95]

NM, I guess since you do have @abstractmethod decorators for some of the methods, you have no choice but to make it an ABC and I guess this makes it clearer that one is not to create an instance of a ServiceHandler

[wgifford]

Though, I suppose this line: handler, e = ServiceHandler.load(model_path) is a bit odd, given ServiceHandler is abstract?

[ssiegel95]

This looks sensible.