Removal of obsolete CloudEvent Factory/Validator etc. #184
Description
Originally, uProtocol was supposed to use CloudEvents as the generic format for all messages to be passed around. However, quite some time ago, we have defined the UMessage type as the generic container for all message data being passed around. CloudEvents today is merely one possible UMessage encoding at the transport level. However, all client facing APIs use UMessage as the parameter type, which means that under normal circumstances application developers will never need to create or touch a CloudEvent at all. The mapping of UMessages to CloudEvents will happen inside concrete transport implementations (if at all).
It therefore seems reasonable to replace the application developer facing utility classes for creating and validating CloudEvents with some low-level utility classes for mapping between UMessage and CloudEvents as defined in the latest version of the transport level CloudEvent mapping specification.
This will allow us to get rid of a lot of legacy code that is hard to maintain and does not serve any real purpose.
We had already briefly discussed this during our weekly community meeting today and agreed to remove/replace the existing helper classes.
@PLeVasseur @stevenhartley @AnotherDaniel @ValMobBIllich WDYT?