You can do this, depending on your definition of "async" from the GUI.
Zope isn't very asynchronous. The method calls occur within a thread.
These threads and the twisted library do not play well together in the
version of zope we are using.
You could add an XML-RPC interface that would find your collector
registered in ZenHub and make requests. This is one way that
distributed RRD data and graph rendering works. See
ZenHub/services/ZenRender.py.
It isn't meant to be simple or illustrative, but zenrender supports "get
me the current value from an RRD file" using the XMLRPC request on port
8090. Fire up ZenHub, connect with zenrender. The service in ZenHub
opens port 8090, and listens for xmlrpc (and http) requests. You can
use XML/RPC calls against this server to reach back through zenhub and
out to zenrender to pull data from remote rrd files. We use this
configuration when collection is being done on the far side of a firewall.
-Eric
kpg123 wrote:
I'm looking for an example of how to perform an action from the GUI to asynchronously notify a daemon to perform an action and return a result. For example, if the user were to select a dialog from a menu item called "Get foobars", have a request with the message "GET FOOBARS id" be sent to the daemon and have a result be sent back so that the dialog can display a list of valid foobars for the user to select.
All of the examples of "communication" I've seen so far have been to invoke a daemon with arguments, and the daemons update the database behind the scenes through twisted calls. I thought that the key might be in zenhub.py, but nothing is making sense to me right now.
Does someone have a simple and illustrative example of how to achieve this functionality?
Thank you!
kells
_______________________________________________
zenoss-dev mailing list
zenoss-dev@zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-dev
_______________________________________________
zenoss-dev mailing list
zenoss-dev@zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-dev
