remoting

问题 It's not possible to set a connection timeout on a .NET remoting call. Documentation occasionally refers to TcpChannel properties that allegedly do this, but discussions and the most recent docs I've found indicate that this is not possible. One may set a timeout on the remoting call itself, but not on the initial connection attempt. You're stuck with the default 45-second timeout. For various reasons I can't use WCF. This causes a problem when the remoting server goes away. If I attempt to

问题 I checked the rest of the remoting questions, and this specific case did not seem to be addressed. I have a .NET Remoting server/client set up. On the server side I have an object with a method that can throw an exception, and a client which will try to call that method. Server: public bool MyEquals(Guid myGuid, string a, string b) { if (CheckAuthentication(myGuid)) { logger.Debug("Request for \"" + a + "\".Equals(\"" + b + "\")"); return a.Equals(b); } else { throw new

问题 I have a WinForms Application (.net 3.5) which displays a list of processes. I would like to be able to attach to one of those processes. I have multiple Visual Studio 2010 instances running and I would like to create a List/Dropdown where I select one of those instances and then attach the Debugger to it. Getting the VS2010 instances shouldn't be too hard, but I have no idea how to invoke the "attach to process" command. I want to avoid SendKeys-Type solutions, so I just wonder if there is

问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 3 years ago . (This is a followup to my previous question about measuring .NET remoting traffic.) When I am testing our Windows service / service controller GUI combination, it is often most convenient to run both pieces on my development box. With this setup, the remoting traffic between the two is via loopback, not through

问题 I have some .NET remoting code where a factory method, implemented in some server side class, returns interfaces to concrete objects, also executing on the very same server. .NET remoting automagically creates proxies and allows me to pass the interfaces across to the client, which can then call them directly. Example interfaces: public interface IFactory { IFoo GetFoo(); } public interface IFoo { void DoSomething(); } Example client code: ... IFactory factory = (IFactory) System.Activator

问题 The code below shows interface and remote object are coded in the same file How to separate them into two files ? Current Code : <s:RemoteObject id="ro" destination="customerService" source="customerService" endpoint="http://localhost/amfphp/gateway.php" showBusyCursor="true"> <s:method name="getCustomer" result="getCustomer_resultHandler(event)"> <s:arguments> <CusOpt>{''}</CusOpt> <option>{''}</option> <idcompany>{2}</idcompany> </s:arguments> </s:method> <s:method name="genPKID" result=

问题 A server listens on a port, waiting for incoming requests from clients (the client as a matter of fact is an ejb). These requests pass a complete object model as parameter (e.g. a list of Employees, each Employee a list of Tasks etc.). Now the server has to start another java program in a new JVM instance on the same machine, with this object model as a parameter. This other java program should be a standalone java program, but I cannot pass the object model as a parameter to the main method

问题 Up until this point all the .NET remoting code I have written or worked with has been exposed as SingleCall. I ran across a .NET remoting component hosted in a Windows service that is exposed as a Singleton. This object has the potential to be called by more than one client at the same time, and it has no locks or other provisions to protect its internal state. If I understand Singleton correctly then this has the potential for big problems correct? 回答1: No more potential than a SingleCall

问题 This application publishes its own address for other systems to connect to using .net remoting. It gets all the addresses of the computer with something like: IPAddress[] IPList = Dns.GetHostEntry(Environment.MachineName).AddressList; string ipAddress = IPList[ipIndex].ToString(); if(ipAddress.contains(":")) { // ip6 address url = "tcp://[" + ipAddress + "]:" + port + "/" + name; } else { url = "tcp://" + ipAddress + ":" + port + "/" + name; } I added the square brackets in case it was

问题 What's the easiest way to get RPC in .NET? I see that there is .NET Remoting and WCF, and according to Wikipedia, WCF is the successor to .NET Remoting. So far, I only tried the remoting stuff, which seems to be pretty simple -- I also didn't hit any problem with the application speed so far. Is .NET remoting really the best way to get RPC working, or should I look into WCF (as .NET remoting is going to be discontinued in favor of it?)? I only want communication with already known objects