The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,947 other followers

Archive for October 28th, 2015

“Docker in Production” Developer Person learns: Production and operations are…

Posted by jpluimers on 2015/10/28

Quote of the day: Kristian Köhntopp:  Operations exist because one does not simply run an app.

Good night all (:

–jeroen

via: “Docker in Production” Developer Person learns: Production and operations are…

Posted in Uncategorized | Leave a Comment »

network, multicast and send address in TransportNetwork; via Digging into Tibco Rendezvous network details – II

Posted by jpluimers on 2015/10/28

Tibco is very powerful and can do all sorts of casting.

For my memory (formatted for readability; there are more details at OpenPGM Concepts : Transport):

The network parameter consists of up to three parts, separated by semicolons—network, multicast groups, send address—as in these examples:

Example Meaning
lan0 network only
lan0;225.1.1.1 one multicast group
lan0;225.1.1.1,225.1.1.5;225.1.1.6 two multicast groups, send address
lan0;;225.1.1.6 no multicast group, send address

The format is like this:

partOne;partTwo;partThree

and some bits are optional

partOne[;[partTwo][;[partThree]]]

Part one identifies the network, which you can specify in several ways: – Host name, Host IP address, Network name, Network IP number, Interface name, Default TRDP daemons use the network interface which corresponds to the hostname of the system as determined by the C function gethostname(). PGM daemons use the default PGM multicast interface, 224.0.1.78.

Part Two—Multicast Groups – Part two is a list of zero or more multicast groups to join, specified as IP addresses, separated by commas. Each address in part two must denote a valid multicast address. Joining a multicast group enables listeners on the resulting transport to receive data sent to that multicast group.

Part Three—Send Address, Part three is a single send address. When a program sends multicast data on the resulting transport, it is sent to this address. (Point-to-point data is not affected.) If present, this item must be an IP address—not a host name or network name. The send address need not be among the list of multicast groups joined in part two. If you join one or more multicast groups in part two, but do not specify a send address in part three, the send address defaults to the first multicast group listed in part two.

Note: I wasn’t aware that for Tibco Rendezvous the default multi-cast network was 225 (often you see 224 here, as that is the starting multi-cast range in the IANA IPv4 Address Space list)

–jeroen

via:

Posted in Communications Development, Development, Internet protocol suite, Network-and-equipment, Software Development, TCP, TIBCO Rendezvous | Leave a Comment »

 
%d bloggers like this: