> Ok let me explain. In the URI based service dispatcher, lets say we
> have the incoming URL services/foo/Echo. When it give this to
> parseRequestURLForServiceAndOperation method to process, it returns
> value > foo, value > Echo and value > foo/Echo.
> Then it tries to find a service from 'foo'. If so, fine this is the
> existing case (In the URI based operation dispatcher, it will find the
> operation Echo). If there's no service called 'foo', then it tries to
> find a service from foo/Echo (value). If it exists, that is our
> hierarchical serivce.
Make sense, then how about the operation name for the hierarchical
service? is it like /services/foo/Echo/echo ?.
Only worry I have is this is confusing, by looking at the URI it is hard
to tell whether it is a service or operation ("/" is a special character
when for URL and it has its own meaning). That is why I suggested to
follow something like "/services/version-isusru/echo"
"/services/version-azeez/echo". Which does not break anything and you do
not need to do anything to get that working.
> That is how I've done it. The only limitaion is in the scenario in
> which we have two services 'foo' and 'foo/Echo'. In that case,
> priority is given to 'foo' service. But I think it is not common to
> have a service name equal to a folder name.
I think if the service is "version" then it will have directory called