Fix issue #49. Add tests.

[skybardpf]

• Include PhpUnit into project
• Tests for Server\MethodWrapper
• Constructor Server\Server taskes MethodWrapper or array methods.
• Fix issue Method names conflict #49

@marcelklehr Your variant for solving the problem #49 the wrong. Example:

$methods = array(
  '__register' => function($params) {}
);
$server = new Server\Server($methods);
$server->input = '{"jsonrpc": "2.0", "method": "__register", "params": [], "id": 1}';
$server->dispatch(); // Call method "__register" of class MethodWrapper

[marcelklehr]

Originally the idea was that the server should be able to provide the methods of any object (e,g, it would be able to infer the parameter order via reflection etc.), MethodWrapper is just a utility to get things going quickly. Perhaps we should remove it entirely, instead of making it the only choice, because in the end, I think Classes are a better way to write an RPC API than arrays.

[skybardpf]

That is, to make the host an array? Format:

class Foo() 
{
  public function bar() {}
}

$foo = new Foo();

$methods = array(
  'method1' => function() {}, // anonymous function
  'method2' => array($foo, 'bar'), // Method of class
)

new Server($methods);

Declaration:

public function __construct(array $host)

Example:
https://github.com/marcelklehr/tivoka/pull/58/files/710ee26cd637d2df40c83eb2e16364a809e75654#diff-5994b67b081aa8d862f75ca5742fb841R23

[skybardpf]

or I misunderstood? 😄

[marcelklehr]

No, I think it would be better to stop supporting passing hosted methods as an array:

class Foo() 
{
  public function bar() {}
}

$foo = new Foo();

-$methods = array(
-  'method1' => function() {}, // anonymous function
-  'method2' => array($foo, 'bar'), // Method of class
-)

-new Server($methods);
+new Server($foo)