why not call this `ban` if that is the varnish term for the operation? so invalidatePath is a fallback for varnish 2 right?

is there a way we could have just one method applications can call and then the configuration decides if we do varnish 2 or varnish 3 way? it feels wrong to me to force the calling code to hardcode if its varnish 2 or 3. could this method gracefully degrade to do the invalidatePath operation if configured for varnish 2 compatibility? potentially purging too many things like ignoring content type... then we could deprecate invalidatePath and recommend to always use this method.