Geek Answers Handbook

Network Communication Settings in Java (Client / Server)

There is RMI, which, as I understand it, is a relatively fragile, direct connection between Socket, which is pretty low level, and Strings, which while solid, seem to be metaphorical PHP.

What less basic parameters do I have for Internet-client / server communication? What are the advantages / disadvantages? What are some issues that I should take into account? The recommendations of third-party libraries are in order if they remain platform independent (i.e. do not contain restrictive code).

We are looking for options, not a definite answer, so I leave the details of my own requirements empty.

+1
source share
2 answers

As you pointed out “Internet-based”, there is a lot to say about the HTTP-based, RESTful approach (I highlighted some issues that you should consider):

Pros:

  • You can use / abuse one of the unrelated web-based framework levels for the server side (e.g. Spring MVC , Play! )
  • Perform a low-level operation was performed on the client side (Apache HTTPClient)
  • Plain text protocol easy to debug wire
  • , (, SoapUI) - OR ,
  • (80/443)

:

  • , - "", RESTful
  • Raw , --
  • sniff (SSL )
+2

" "? RMI , , , DNS . , "" , . . RMI , , , "" - . , , . RMI/IIOP , . - , , , RMI/JRMP . , .

0

More articles:


All Articles