Programming Jabber

Add a connector mechanism to the satellite server

Now that we’ve opened up a connection point in the main server, we need to add some corresponding configuration to the satellite server’s XML—the “plug” that will attach to the connection point on the main server:

<jabber>
  <service id="conflinker">
    <uplink/>
    <connect>
      <ip>127.0.0.1</ip>
      <port>9001</port>
      <secret>confsecret</secret>
    </connect>
  </service>
  <service id='conf.yak'>
    <host>conference.yak</host>
    <load><conference>./conference-0.4.1/conference.so</conference></load>
    <conference xmlns="jabber:config:conference">
      ...
    </conference>
  </service>
</jabber>

This new service (the “plug”) with an ID of conflinker (which matches the ID of the corresponding “socket” in the main server)^[8] contains two elements.

• The <connect/> tag, which corresponds to the <accept/> tag in the main server’s configuration.

• The <uplink/> tag, which serves as a conduit for all types of packets—those handled by each of the three delivery trees log, xdb, and service.

While we’re looking at the satellite server’s configuration again, it’s worth pointing out that even in a situation in which the satellite server process would be running on a separate host (we’re running it here on the same host—hence the localhost IP address of 127.0.0.1 in the <accept/> tag), the value of the conference service’s host filter is still conference.yak. In other words, the name of the host where the satellite server actually runs is irrelevant. This is because the conference ...