Yes, RMI introduces lag overhead, have you had any experience with Java using the basic socket libraries? Do they have the same problem?
Java use may introduce some lag, but you probably will have your system up and running faster and on many platforms -- you can find the bottlenecks and work out reasonable solutions.
You may want to consider Java using RMI, Java is more road tested for distributed applications than C# and the RMI library would help raise the abstraction level for the network programming. Bruce Eckel puts out a good intro book (also on-line) for Java if you don't know Java and O'Reilly puts out a decent RMI book.
Also consider that Java would allow instant support to all Windows, Mac, Linux, and Unix platforms--a real benifit I think.
Slashdot Mirror
Yes, RMI introduces lag overhead, have you had any experience with Java using the basic socket libraries? Do they have the same problem?
Java use may introduce some lag, but you probably will have your system up and running faster and on many platforms -- you can find the bottlenecks and work out reasonable solutions.
You may want to consider Java using RMI, Java is more road tested for distributed applications than C# and the RMI library would help raise the abstraction level for the network programming. Bruce Eckel puts out a good intro book (also on-line) for Java if you don't know Java and O'Reilly puts out a decent RMI book.
Also consider that Java would allow instant support to all Windows, Mac, Linux, and Unix platforms--a real benifit I think.
Good Luck