remoting

I'm new to both Web Services and RMI and I wonder which is the better way to do remoting between different web applications, when these applications are all written in Java, that is when different programming languages don't matter (which would be the advantage of WS). While on the one hand I would guess that there's a performance overhead when using web services (does anyone have some numbers to prove that?), on the other hand it seems to me that web services are much more loosely coupled and can be used to implement a more service-oriented architecture (SOA) (which isn't possible with RMI,

I want to use c# and WMI to start a process remotely in another computer. I've made some initial research and found out that i ultimately have to use a processclass. The "Win32_Process" was the first thing that seemed obvious to be used, however, it seems it is limited to represent only local processes. What other Windows process classes can I use? Here is what the code when using Win32_ScheduledJob class: static public String RemoteConnect() { try { ConnectionOptions conn = new ConnectionOptions(); conn.Username = @"JV"; conn.Password = @"Nazpal6180"; conn.EnablePrivileges = true; conn

I have a problem, I have a script which: Connect with PSSession (I use PSSession with admin account) Stop 2 process Do change on them files Start the 2 process (Problem here) I want to start process on server, so i'm connect with PSSession (No problem) I do Invoke-Command : # $pathProg path to my program Invoke-Command -session $mySession -command {Start-Process $($args[0])} -ArgumentList $pathProg But it does nothing (I verify with VNC) I do Invoke-Command too : # $pathProg path to my program Invoke-Command -session $mySession -command {&$($args[0])} -ArgumentList $pathProg It lauch the

I have been trying to get the following code to work(everything is defined in the same assembly) : namespace SomeApp{ public class A : MarshalByRefObject { public byte[] GetSomeData() { // } } public class B : MarshalByRefObject { private A remoteObj; public void SetA(A remoteObj) { this.remoteObj = remoteObj; } } public class C { A someA = new A(); public void Init() { AppDomain domain = AppDomain.CreateDomain("ChildDomain"); string currentAssemblyPath = Assembly.GetExecutingAssembly().Location; B remoteB = domain.domain.CreateInstanceFromAndUnwrap(currentAssemblyPath,"SomeApp.B") as B;

hello, We have large environment with hundreds of virtual machines. During our services deployment we need to copy some files from build drop to all these machines. So, we have: User machine, where deployment scripts executing Build drop machine, where files are Target machine Powershell is used as script language. Something like: $buildDrop = "\\sourceMachine\Build" $machineTarget = "targetMachine" Invoke-Command -ComputerName $machineTarget -ArgumentList $buildDrop -ScriptBlock { Param( $buildDrop ) Test-Path $buildDrop # Will return False } This approach leads to double hop issue , which I