make ros api services local about rosbridge_suite

[T045T]

Having rosapi global makes sense insofar as it provides an API to global ROS facilities. I'm not sure what launching it inside a namespace would mean, semantically. Wouldn't /foo/rosapi and /bar/rosapi do exactly the same thing (i.e. provide the same response to identical service requests)?
If so, I see no need to run two (or more) instances of the node.

[rctoris]

I agree with @T045T. In most cases, I fully support local namespaces. But running two of this node will have no effect of make any sense as it truly is global.

[jihoonl]

It is not a matter of having multiple instance of rosapi. It is about how to utilise node namespace. It expects that /rosapi namespace is always reserved for rosbridge and not used by any other node. It is pretty dangerous assumption and losing flexibility of library.

User should have a right to choose whether it is globally namespaced or locally namespaced. Is there any other reason rosapi should be global namespace?

[T045T]

Good point about other nodes using the rosapi namespace. But I still think rosapi should treat its services like tf nodes treat the /tf topic - always global, even if the node is launched inside a namespace. The user can still manually remap services if they conflict with other nodes.

To allow for that case, ROSLIB.Ros should probably have a rosapiName parameter that defaults to "/rosapi"

[jihoonl]

Your points are correct and I don't have actual usecase which proves necessity of namespace.

Let's keep this as global. I will re-open this when I find an usecase.

[jihoonl]

This decision would help to close these issues.

#115
RobotWebTools/roslibjs#58