At the moment all of our Server adapters (which are passed to its constructor as rawServer argument) are using composition to store the original server object, which is being created in the same place using methods similar to those original server object has.
It results in a lot of boilerplate code and usage of workarounds which can be avoided by inheriting the adapters from the classes used in an underlying implementation now.
At the moment all of our Server adapters (which are passed to its constructor as
rawServerargument) are using composition to store the original server object, which is being created in the same place using methods similar to those original server object has. It results in a lot of boilerplate code and usage of workarounds which can be avoided by inheriting the adapters from the classes used in an underlying implementation now.This will obviate PRs like https://github.com/metarhia/jstp/pull/190 and should we decide to go with the proposed approach, it will make sense to close the PR.
@metarhia/jstp-core, what is your opinion on the topic?