http://www.tldp.org/HOWTO/Multicast-HOWTO-9.html
My explanation was bad, it's due to my orrible English skills... :-|
I don't know if it could be a good idea, and therefore this is why I'd like to have yours opinions.
It should be possible to write a separate program/utility that check the servers availability using multicast (sure, at udp level).
Every servers send messages over multicast to join the group, at this point the client knows exactly how many servers there are and a new configuration file could be written, and the build can begin.
In this way you can also have different building farms only using a different multicast group.
i.e.
237.0.0.1 5555 1st Compiling farm for i386 architecture
237.0.0.10 4444 2nd Compiling farm for Sparc architecture
and so on...
Again, I don't know if this a good idea, I like it because I'm working with multicast based application every days, and so I'm obsessed about it.
In the hope my explanation is better :-)
Thanks a lot
Regards
Antenore.
2006/2/7, Martin Pool <[EMAIL PROTECTED]>:
On 6 Feb 2006, Antenore Gatta <[EMAIL PROTECTED]> wrote:
> Hi Martin,
>
> > distcc uses tcp connections to carry the requests and responses, and
> > multicast doesn't work with tcp, only udp. multicast udp could be good
> > for checking the load of servers or seeing if they have a cached result.
> Why not? Multicast is very usefull in this situation, all the
> clustered environment are using multicast to join member to the
> cluster.
Why not use multicast for tcp? Because as far as I know there's no
specification for how it would work, and no network stack supports it.
:-)
--
Martin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFD6GA4PGPKP6Cz6IsRAhOjAJ0W9gfneJOk3TBTwuz+lN0kvFtJ5QCeK1g2
0doxO9LzGasX3nOIyRplIgc=
=KT63
-----END PGP SIGNATURE-----
__ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/distcc
