-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jesse Keating wrote: > On Sat, 2006-06-24 at 15:57 -0500, Clark Williams wrote: >> Hmm, that would mean that mock would have to be an XML-RPC server. I >> like XML-RPC, but that might be a bit more complicated than is >> strictly needed. > > Does it really have to be a server? Could it be a push rather than a > poll? Mock could make xml-rpc calls to whatever wraps around it.
I've used XML-RPC to implement services a couple of times now. Both times it's been python to python, with a python client talking to a python server running under mod_python in Apache. I'm not sure how you would implement XML-RPC in a push mode, since someone has to provide the remote procedure call service and someone has to call it. I really like XML-RPC as a an RPC mechanism, but I think it's a bit of overkill for this. To do it as an RPC, we would have to listen on a socket for someone to ask "what's your state?" and reply with the current state of the build. I'd say it's much simpler to "publish" the state to somewhere that anyone who cares (e.g. plague) can read it. I'm still thinking shared memory, but there may be another mechanism (a simpler one) that I'm missing. Clark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFEn/JNHyuj/+TTEp0RAvkfAKCtVH1PFgjZpiRjoxUN39OgmixgRgCfYdjc thQQ7taYOGJ8KYST6KKRf3U= =m26z -----END PGP SIGNATURE----- -- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
