Erlang\Util violates Single Responsibility Principle

[HelloGrayson]

Looking at the Erlang\Util test case indicates the class has clearly too much responsibility. In an effort to make this area of the app more testable, the following structure is desirable as a starting point:

<?php

namespace Hurricane\Erlang\Util;

interface Encodable {}
interface Decodable {}

class Encoder implements Encodable {}
class Decoder implements Decodable {}

Leaving the classes as static would be the easiest first move. Also, if leaving static, it's possible that interfaces aren't immediately beneficial.

[icheishvili]

This is in fact the way that the Java driver works, so it's probably right to at least split this up into two parts.

[HelloGrayson]

good deal - I'll look at the Java driver when refactoring