用于删除SourceSafe绑定的实用工具？(Utility for removing SourceSafe bindings?)

 如何调用x取决于它的API以及x是否与y在同一节点中运行。 
 
 
 
 如果x在与y相同的节点中运行，并且声明了应用程序依赖关系，使得x在y开始之前启动，则可以简单地调用x的模块，与调用任何其他本地模块相同。 
 
 
 如果x在不同的节点中，那么是的，使用rpc模块调用它是一个可行的选择。 只要y节点可以通过分布式Erlang连接到x节点， rpc就可以在没有任何额外设置的情况下工作。 
 
 
 我提到了API，因为通常情况下模块通过将其进程ID注册到某种名称注册表来完成其工作，例如通过erlang:register/2 ， 全局注册表或其他注册表（如gproc） erlang:register/2本地注册表，以及呼叫者可能需要首先直接或间接访问注册表以找到他们试图呼叫的目标。 例如，在调用gen_server实例时 ，通常需要将要尝试调用的实例的名称或pid作为参数传递，对于远程调用，还需要目标节点名称。 

How you call x depends both on its APIs and on whether or not x is running in the same node as y.
 
 
 
If x is running in the same node as y and your application dependencies are declared such that x starts before y starts, you can simply call into a module of x the same as calling any other local module.
 
 
If x is in a different node, then yes, using the rpc module to call into it is one viable option. As long as the y node can connect to the x node via Distributed Erlang, rpc will work without any extra setup.
 
 
I mention the API because it's frequently the case that modules do their work by registering their process ids into some sort of name registry, such as the local registry via erlang:register/2, the global registry, or alternative registries such as gproc, and callers may need to first access the registry directly or indirectly to find the target they're trying to call. For example, when calling a gen_server instance you typically need to pass as an argument the name or pid of the instance you're trying to call, and for remote calls, the target node name is needed as well.