IIOP and SOAP are marshalling protocols/message formats. You can build entirely different frameworks around either one of these marshalling protocols.
JRMP is not a transport protocol, but a request dispatcher, IMHO. So, when Marc and Scott pull apart RMI from EJBs, JRMP will still exist, but there will be RMI, RMI-IIOP, CORBA(IIOP), Servlets(XML-RPC, SOAP) JMX beans/connectors/whatever listening for requests and passing them on to the Objects that can dispatch them. Please let's not get into a terminology battle. I will lose it terribly :) Bill > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Jung , Dr. > Christoph > Sent: Wednesday, October 31, 2001 10:20 AM > To: '[EMAIL PROTECTED]' > Subject: AW: [JBoss-user] Jboss and JRMP > > > -----Ursprüngliche Nachricht----- > >Von: Bill Burke [mailto:[EMAIL PROTECTED]] > >Gesendet: Montag, 29. Oktober 2001 17:23 > >An: Ben Hui; Jboss-User@Lists. Sourceforge. Net (E-mail) > >Betreff: RE: [JBoss-user] Jboss and JRMP > > >JRMP is not a transport protocol. RMI is the transport protocol. > > Hmmm, but why do people then talk about RMI-over-IIOP or RMI-over-SOAP, > where IIOP and SOAP are certainly > transport protocols? > > CGJ > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
