Best practice for naming an argument that can mean 3 different things
<p>Consider this... I am writing a class named Cache which will accept either a path to a file/url or a string. I am going to use PHP's functions such as <code>parse_url()</code> and <code>is_file()</code> to determine which input I am receiving.</p>

<p>here is my example, in PHP</p>

<pre><code>class Cache {
    public function __construct($pathUriOrString) {

    }
}
</code></pre>

<p>What is the best practice for naming this argument? Is this even a valid way of creating an class, or should this be a base class and have separate classes that extend it?</p>

<p>I got this idea from <a href="http://code.google.com/p/php-image/" rel="nofollow">php image</a> where the construct either receives one argument (a path) or 2 arguments (a width and height).</p>

<p>So, am I on the right track, and if so, what is best practice for naming an argument which takes different inputs (and won't confuse another developer down the track?)</p>
