DDD for HTTP resources

[migduroli]

• Domain-driven design for HTTP resources #145

[migduroli]

In trying to follow the same structure as we have for SQLAlchemyTableRepository, which contains a manager SQLAlchemyTableManager which is the one managing the execution of queries with the _connection object, we have created:

• HTTPResourceManager
• HTTPResourceRepository which derives from HTTPRepository and has a _resource_manager = HTTPResourceManager(self._resource, client).

However, following this pattern I find that the methods of HTTPResourceRepository are just wrappers of single-line methods of HTTPResourceManager. Does this mean we might not need HTTPResourceManager? Or, contrarily, does this mean the methods fo HTTPResourceManager need to do something else rather than jusr returning the response of the client?

[migduroli]

In trying to follow the same structure as we have for SQLAlchemyTableRepository, which contains a manager SQLAlchemyTableManager which is the one managing the execution of queries with the _connection object, we have created:

• HTTPResourceManager
• HTTPResourceRepository which derives from HTTPRepository and has a _resource_manager = HTTPResourceManager(self._resource, client).

However, following this pattern I find that the methods of HTTPResourceRepository are just wrappers of single-line methods of HTTPResourceManager. Does this mean we might not need HTTPResourceManager? Or, contrarily, does this mean the methods fo HTTPResourceManager need to do something else rather than jusr returning the response of the client?

Solved! The HTTPResourceManager will return the data itself, i.e. will wait for the response and run checks of the status_code. If the status_code satisfies the standard REST response codes, then it will parse the data (if available). Otherwise, it will raise an appropriate exception.