Java comes with a servlet that makes it possible to use RMI over HTTP, however it's hard to use and has limitations like not be able make calls back to other remote objects.
This implementation is easy to use, and full featured. Anything you can do anything with normal RMI you can do with webRMI-based RMI.
Also comes with a servlet-based RMI registry implementation. Enables you to host an RMI registry in a web server.
webRMI implements a completely HTTP-based RMI architecture by...
providing a custom HTTP-based RMI socket layer (RMI has a pluggable socket layer that separates the protocol layer from the rest of the RMI implementation). providing an HTTP-based RMI registry that is implemented as a servlet (this means that you don't need to use the rmiregistry utility to obtain access to webRMI's RMI objects, clients can discover available applications by looking them up in WebRMI's HTTP-based registry). providing a custom JNDI service provider that implements HTTP-based access to RSWT's custom Servlet-based RMI registry.
Use Patent Claims
These details are provided for information only. No information here is legal advice and should not be used as such.