Proxy name should be differentiated based on the proxy capabilities

[Ocramius]

A proxy class intercepting doFoo and a proxy class intercepting doBar should have different naming to avoid collisions. Same applies for different proxy types. The naming strategies should be tweaked to handle this.

[Ocramius]

Currently, this affects also co-existing proxies coming from different factories.

For example, following code will cause an exception:

<?php

require __DIR__ . '/../vendor/autoload.php';

class Track
{
}

$config   = new \ProxyManager\Configuration();
$factory  = new \ProxyManager\Factory\HydratorFactory($config);
$hydrator = $factory->createProxy('Track');
$config  = new \ProxyManager\Configuration();
$factory = new \ProxyManager\Factory\AccessInterceptorValueHolderFactory($config);
$proxy   = $factory->createProxy(
    new Track,
    array('getProject' => function () { echo "Query completed!\n"; }),
    array('getProject' => function () { echo "Query completed!\n"; })
);

That happens because the hydrator is generated and then re-used immediately in the second factory instead of an access interceptor.