On Mon, 2006-06-26 at 09:42 -0500, Clark Williams wrote: > 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. >
What about using dbus? Its not "simple" per se, but should scale pretty well and allow for pretty good interaction. -- Jesse Keating RHCE (geek.j2solutions.net) Fedora Legacy Team (www.fedoralegacy.org) GPG Public Key (geek.j2solutions.net/jkeating.j2solutions.pub)
signature.asc
Description: This is a digitally signed message part
-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
