[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster] mechanisms for client connection

For XB,
"SOCKET" is referring to a xmlBlaster proprietary protocol, not a UNIX domain or TCP socket: http://www.xmlblaster.org/xmlBlaster/doc/requirements/protocol.socket.html.

As a middleware platform, XB support other protocols so that clients can connect from many different languages and platforms:


CORBA is just yet another protocol to do cross-platform RPC -- some older J2EE servers like Websphere 3.5 used it. It still has niche popularity.

XMLRPC is a another protocol to do RPC over XML, this existed before SOAP, which also will eventually by supported by XB.

RMI is a Java-specific RPC protocol

and so on. All these protocols can bind to any arbitrary port as specified in the xmlBlaster.properties file. So in my case, I start up a XB instance with socket running on port 7607, xmlrpc on 7900. My C clients use the socket protocol to pub/sub messages, my perl clients use xmlrpc to connect. You could start up a RMI server and also have java clients join in on the fun. Or java/C/perl clients could use CORBA for increased performance, per the performance tests posted on the website.

Hope this helps

On 11/15/04 17:35, Viner, David wrote:

I'm trying to understand some of the internals of XMLBlaster.  When a client
connects to the xb server, it appears it can connect via at least 2
different protocols types "CORBA" and "SOCKET".

are there other connection types?
I don't have a lot of familiarity with corba, so, please forgive me if this
is a silly question... is the corba connection via a socket? if so, what is
the socket type (stream socket vs. datagram socket)?  and what is the port
through which xb clients will communicate with the xb server?