EJB design: RMI As A Layer To Communicate With EJB

  1. RMI As A Layer To Communicate With EJB (2 messages)

    I would like to know whether its a good idea to use RMI as the communication layer to let my Swing Application Client talk to EJB.

    In this secenario, the Swing Application is a client to the RMI and RMI the client to the EJB. I return the values from the EJB to the RMI which in turn returns the values to the Swing client.

    The reason for the above architechture is essentially speed. I compared Direct EJB Client,RMI and XMLRPC and I found that RMI to be faster than the others.

    Now I would like to know from the developers fraternity whether it is ok for me to go ahead with this(Just a second opinion). I shall be more than glad to recieve inputs on this regard.

    Thanks And Regards
  2. I don't understand your posting. EJB is based on RMI as the underlying transport.

  3. Yes EJB is built on top of RMI. But my point is instead of have RMI overheads that occur when direct EJB client are used, we can directly start off at the RMI layer and have a performance boost.