RMI or sockets?

[Murphy Patrick]

Hello,
I am wondering what the relative advantages/disadvantages of using RMI vis-a-vis sockets for the assignment.
Which one is easier to code?
Which one creates cleaner/neater code?
What about debugging ease?
Thanks for any comments.

[Ian B Anderson]

Hello,
Just search this forum with "RMI v Sockets" as the criteria to match.
Ian

[Mike Wiegand]

Hi Murphy Patrick or is it Patrick Murphy??
Do yourself a giant favor and use RMI. RMI will save you the overhead of having to establish an object protocol as well as adding server logic that keeps track of connected clients. Sockets communicates to remote machines by passing objects back and forth whereas RMI does not. RMI is also the basis or EJBs, so if you plan on continuing with architecture stuff, RMI will probably provide a better foundation. Sockets would be cool to implement, but the associated overhead sure adds to the already large task of the FBN application. Good luck

[gulshan grover]

i dont know ab ur application but i think rmi is always better than socket programming and easier to program. i have worked on both and found rmi very easy as compared to sockets.

[Murphy Patrick]

Originally posted by Mike Wiegand:
Hi Murphy Patrick or is it Patrick Murphy??

It is Patrick Murphy.
The registration won't take that so I used my last name first
Thanks for your comments. Makes the choice easier for me.
-Pat