Ah, you're also looking at coreapps/examples/monitor.py I was referring to netapps/monitoring.py (you can find that in the destiny branch) (monitor.py is a much simpler, early monitoring component)
On Thu, Dec 8, 2011 at 10:26 AM, Shrutarshi Basu <ba...@cs.cornell.edu>wrote: > Thanks, it looks like I am working with an older version of NOX -- I can > see a monitor.py app that does not seem to use the xid at all. I will try > to upgrade and see what I can do. Will report back. > Thanks, > Basu > > > On Wed, Dec 7, 2011 at 4:27 PM, Kyriakos Zarifis <kyr.zari...@gmail.com>wrote: > >> Hi Shrutarshi, >> >> the field you should be looking at is the xid (transaction id). >> I don't remember the specifics right now - I think in Destiny it is >> automatically set (and returned?) and you can also set it when you send the >> request (that's what the monitoring module does) >> >> I can be more specific when I look at the code to refresh my memory, but >> this might help for now >> >> On Wed, Dec 7, 2011 at 12:29 PM, Shrutarshi Basu <ba...@cs.cornell.edu>wrote: >> >>> If I send a bunch of aggregate stats requests for different flows, is >>> there a way for the aggregate_stats_in handler to know which response it is >>> being called on? I see that it gets the dpid, but what if I have multiple >>> flows on the same dpid that I want information on? >>> Thanks, >>> Basu >>> >>> -- >>> -- >>> Shrutarshi Basu >>> Basus.me >>> The ByteBaker <http://bytebaker.com> -- because Computer Science is not >>> about computers >>> >>> >>> _______________________________________________ >>> nox-dev mailing list >>> nox-dev@noxrepo.org >>> http://noxrepo.org/mailman/listinfo/nox-dev >>> >>> >> > > > -- > -- > Shrutarshi Basu > Basus.me > The ByteBaker <http://bytebaker.com> -- because Computer Science is not > about computers > >
_______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
